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

diff and sync commands fail with "entity already exists" if global plugins in multiple workspace yaml files exist #195

Open
kallecaco3 opened this issue Aug 4, 2020 · 4 comments
Labels

Comments

@kallecaco3
Copy link

After dumping all workspaces in a Kong EE environment using:

deck dump --all-workspaces

deck diff --state ./
fails with:
Error: inserting plugins into state: entity already exists

If multiple workspaces contain the same glob al plugin, e.g. file-log or correlation-id

To work around this issue it is necessary to follow the recommendation to manage of one workspace at a time and not club configuration of all the workspaces at the same time: https://deck.yolo42.com/guides/kong-enterprise.html

@hbagdi
Copy link
Member

hbagdi commented Aug 4, 2020

What is the question here? I understand that you ran into a problem and then solved it.

@kallecaco3
Copy link
Author

@hbagdi can we change deck to allow all workspaces to be updated even when clubbing the configurations?
If not, can we make it clearer in the documentation that the workspaces should be diff/sync-ed individually?

@hbagdi hbagdi added the docs label Aug 7, 2020
@hbagdi
Copy link
Member

hbagdi commented Aug 7, 2020

That's very reasonable.
We will fix this unless there is a PR to fix this first.

@stale
Copy link

stale bot commented Mar 20, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Will be closed unless advocated for within 7 days label Mar 20, 2021
@stale stale bot closed this as completed Mar 27, 2021
@hbagdi hbagdi reopened this Mar 29, 2021
@stale stale bot removed the stale Will be closed unless advocated for within 7 days label Mar 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants