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

fix: do not inject plugin.RunOn when Kong >= 2.0.0 #522

Merged
merged 1 commit into from
Jan 31, 2020

Conversation

hbagdi
Copy link
Member

@hbagdi hbagdi commented Jan 29, 2020

Kong 2.0.0 removed the run_on property on the plugins entity.
Controller's code always injects it avoid false positives during diffs.

The change nils the property for kong 2.0 and above only to avoid any
effect on Kong Enterprise, which follows a different versioning scheme.

Fix #521

Kong 2.0.0 removed the `run_on` property on the `plugins` entity.
Controller's code always injects it avoid false positives during diffs.

The change nils the property for kong 2.0 and above only to avoid any
effect on Kong Enterprise, which follows a different versioning scheme.
Copy link

@jfrancisco0 jfrancisco0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can confirm this patch fixed my issue 💯

@hbagdi hbagdi merged commit 8aea90b into master Jan 31, 2020
@hbagdi hbagdi deleted the fix/kong-2.0-compat branch January 31, 2020 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using plugins needing config with Kong 2.0.0 is broken
2 participants