Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to sync config file as the "desired state" (except consumers) #52

Open
486 opened this issue Oct 27, 2016 · 0 comments
Open

Option to sync config file as the "desired state" (except consumers) #52

486 opened this issue Oct 27, 2016 · 0 comments

Comments

@486
Copy link

486 commented Oct 27, 2016

Hi,

For updating live deployments I would like to use kongfig to put my kong apis and their plugins in a "desired state". This would include removing apis or plugins that are no longer present in my config.yml.

Currently, kongfig just adds / updates objects and only when you explicitly use the ensure: "removed" directive it would delete stuff. But for a deployment it is very tedious to track what to delete - you can easily miss something or the config.yml gets polluted with all the things you ever deleted (so you can upgrade from any point).

Of course you could just delete all the apis and then apply the config.yml, but this would potentially equal a tiny service outage because kong doesn't know any apis for a short time. That's not desirable.

The solution would be a kongfig apply --exact command that would add, update and delete api and plugin definitions until it is exactly the same as defined in the config.yml.

The exception of course would be consumers - you generally don't touch them as they are probably managed by some other service. This could be the default or re-use the flag --ignore-consumers.

dgarlitt added a commit to dgarlitt/kongfig that referenced this issue Dec 6, 2017
This adds the ability to use the --force argument to meet the needs of
the feature requested in: mybuilder#52

Removes the need for `ensure: "removed"` in configuration files.
dgarlitt added a commit to dgarlitt/kongfig that referenced this issue Dec 6, 2017
This adds the ability to use the --force argument to meet the needs of
the feature requested in: mybuilder#52

Removes the need for `ensure: "removed"` in configuration files.
dgarlitt added a commit to dgarlitt/kongfig that referenced this issue Dec 6, 2017
This adds the ability to use the --force argument to meet the needs of
the feature requested in: mybuilder#52

Removes the need for `ensure: "removed"` in configuration files.
dgarlitt added a commit to dgarlitt/kongfig that referenced this issue Dec 6, 2017
This adds the ability to use the --force argument to meet the needs of
the feature requested in: mybuilder#52

Removes the need for `ensure: "removed"` in configuration files.
dgarlitt added a commit to dgarlitt/kongfig that referenced this issue Dec 9, 2017
This adds the ability to use the --force argument to meet the needs of
the feature requested in: mybuilder#52

Removes the need for `ensure: "removed"` in configuration files.
dgarlitt added a commit to dgarlitt/kongfig that referenced this issue Dec 9, 2017
This adds the ability to use the --force argument to meet the needs of
the feature requested in: mybuilder#52

Removes the need for `ensure: "removed"` in configuration files.
dgarlitt added a commit to dgarlitt/kongfig that referenced this issue Dec 9, 2017
This adds the ability to use the --force argument to meet the needs of
the feature requested in: mybuilder#52

Removes the need for `ensure: "removed"` in configuration files.
dgarlitt added a commit to dgarlitt/kongfig that referenced this issue Dec 9, 2017
This adds the ability to use the --force argument to meet the needs of
the feature requested in: mybuilder#52

Removes the need for `ensure: "removed"` in configuration files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants