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

Spinnaker-Backend - Remove pipeline from Spinnaker give a name change - planning #60

Open
eyal-mor opened this issue Feb 27, 2023 · 0 comments
Labels
Backend-Spinnaker The issue is related to the built-in Spinnaker Backend documentation Improvements or additions to documentation enhancement New feature or request Shore-CLI Related to the Shore-CLI visualization layer (the CLI itself)

Comments

@eyal-mor
Copy link
Contributor

Give a name change, pipelines will remain orphaned in an application.
This could cause confusion or worse, a trigger of the wrong pipeline may produce inconsistent application states in prod.

To mitigate these problems we must be able to remove unused pipelines during the save command.

Plan out the implications of such a "fix" and a mitigation for the possible errors.

@dkirillov dkirillov added documentation Improvements or additions to documentation enhancement New feature or request Shore-CLI Related to the Shore-CLI visualization layer (the CLI itself) Backend-Spinnaker The issue is related to the built-in Spinnaker Backend labels May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend-Spinnaker The issue is related to the built-in Spinnaker Backend documentation Improvements or additions to documentation enhancement New feature or request Shore-CLI Related to the Shore-CLI visualization layer (the CLI itself)
Projects
None yet
Development

No branches or pull requests

2 participants