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.

Sign up for GitHub

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

Jump to bottom

Terraform Upgrade: Document analysis of recommended path for the upgrade #98289

Closed
2 of 3 tasks
Tracked by #98290
AshleyGuerrant opened this issue Dec 3, 2024 · 1 comment
Closed
2 of 3 tasks
Tracked by #98290

Terraform Upgrade: Document analysis of recommended path for the upgrade #98289

AshleyGuerrant opened this issue Dec 3, 2024 · 1 comment
Assignees
@flooose
Labels
2024 devops practice area categorization -- NOT a team assignment platform-product-team

Comments

@AshleyGuerrant
Copy link

AshleyGuerrant commented Dec 3, 2024 •
edited by flooose
Loading

Issue Description

So that we can run security upgrades in our Redis clusters without the risk of Terraform crashing on Mac OS, Terraform needs to be upgraded. Document an analysis of why the recommended upgrade path was selected, potential risks, challenges, etc.

Tasks

  • Research and discovery
  • Complete documentation

Acceptance Criteria

  • Confluence documentation analyzing the "why" and technical considerations of the recommended Terraform upgrade path.
@AshleyGuerrant AshleyGuerrant added 2024 devops practice area categorization -- NOT a team assignment platform-product-team labels Dec 3, 2024
@AshleyGuerrant AshleyGuerrant mentioned this issue Dec 3, 2024
Open
8 tasks
@AshleyGuerrant
Copy link
Author

Standup note: documentation is finished and feedback has been provided. Closing this ticket out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flooose flooose

Labels
2024 devops practice area categorization -- NOT a team assignment platform-product-team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@flooose @AshleyGuerrant