Provide option to force kong to sync with config #107
Conversation
dgarlitt
force-pushed
the
sync-kong-with-config
branch
from
d90d358 to
632f278
Compare
|
Thanks for this, I'll pull it down and have a look. |
dgarlitt
force-pushed
the
sync-kong-with-config
branch
from
632f278 to
a53faf3
Compare
|
@CyExy I just pushed an update with the test fixture reduced down to just the necessary fields so it's easier to sift through. I also reorganized the unit tests and clarified their descriptions. Let me know if there are any changes to be made. |
dgarlitt
force-pushed
the
sync-kong-with-config
branch
2 times, most recently
from
858527a to
da6a4e1
Compare
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
force-pushed
the
sync-kong-with-config
branch
from
da6a4e1 to
42d4bfa
Compare
|
@CyExy Let me know if there are any issues or concerns with this pull request. I'll be happy to make any modifications. |
|
@dgarlitt Sorry for taking so long, we had a project launch that took all my energy, I had a quick look and got some ideas I'll find some time to think more about it in the coming days. |
|
I haven't tested the code myself, but read through and think it's looking good. Would be keen to hear your ideas, as we may be able to help get them implemented :) |
This adds the ability to use the --force argument to meet the needs of
the feature requested in: #52
Removes the need for
ensure: "removed"in configuration files.