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

Force upgrade from beta to GA 30-days after GA becomes available and decommission beta content & APIs #1451

Closed
susanev opened this issue Sep 5, 2019 · 1 comment
Labels
auth-team anything that needs to be on the auth team board Epic iamv2 This issue or pull request applies to iamv2 work for Automate

Comments

@susanev
Copy link
Contributor

susanev commented Sep 5, 2019

User Story

As an Automate User, when I upgrade to the latest release with the IAM v2 force upgrade, my system will be permanently upgraded to IAM v2. All my data should be safe and any v1 policies should be migrated. If I was already on IAM v2, all my v2 policies should be intact.

My v1 data will be preserved for a period of time (TODO how long?) after the upgrade. Then it will be cleaned up.

Aha! Link: https://chef.aha.io/epics/A2-E-185

@susanev susanev added the auth-team anything that needs to be on the auth team board label Sep 5, 2019
@susanev susanev added Epic iamv2 This issue or pull request applies to iamv2 work for Automate labels Oct 15, 2019
@susanev
Copy link
Contributor Author

susanev commented Dec 7, 2019

closing this, cause its become a release instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auth-team anything that needs to be on the auth team board Epic iamv2 This issue or pull request applies to iamv2 work for Automate
Projects
None yet
Development

No branches or pull requests

1 participant