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

aws/local: Add a choice to preserve gitops/metaphor repos on destroy #1039

Closed
3 tasks
6za opened this issue Jan 2, 2023 · 3 comments
Closed
3 tasks

aws/local: Add a choice to preserve gitops/metaphor repos on destroy #1039

6za opened this issue Jan 2, 2023 · 3 comments
Labels
feature Something new invalid Not a valid issue
Milestone

Comments

@6za
Copy link
Contributor

6za commented Jan 2, 2023

Challenge

  • Add a flag to allow gitops to not be removed on a cluster destroy(on git provider)
  • Add a flag to allow metaphor-x to not be deleted on a cluster destroy(on git provider)
  • How to be able to recycle on install repos on a re-install scenario.

Caveats

  • Some detoken values may change, how to address that situation. How to re-detoken properly.
@6za 6za added this to the Post-1.11 milestone Jan 2, 2023
@6za
Copy link
Contributor Author

6za commented Jan 2, 2023

Some possible scenarios, that it would be important to handle:

  • Disaster Recovery: how to use existing gitops repo as blue-print to a new instance to recover the environment.

  • Some trick infra upgrades scenarios where the host machines are physically upgraded.

@pagottoo
Copy link
Contributor

pagottoo commented Jan 2, 2023

Following...

@fharper fharper added feature Something new invalid Not a valid issue labels Sep 13, 2023
@fharper
Copy link
Contributor

fharper commented Sep 20, 2023

The destroying process is now using a manual deprovisioning for the UI installation, and will also for CLI installation with v2.3 as it will use the API instead of specific CLI code, so this won't be valid anymore. If an user wants to keep the repositories, they just have to NOT run the Terraform git step.

@fharper fharper closed this as not planned Won't fix, can't repro, duplicate, stale Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Something new invalid Not a valid issue
Projects
None yet
Development

No branches or pull requests

3 participants