fix: Docs and Terraform usage after cutting track/2#151
Merged
MichaelThamm merged 9 commits intomainfrom Nov 25, 2025
Merged
Conversation
sed-i
approved these changes
Nov 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
After we created a
track/2branch, we now support deploying our TF product modules fromdev/riskand2/risk. This also means we need to maintain the docs, tests, and modules separately across branches.When upgrading from
2/stabletodev/edge, Grafana refreshes torev174, and fails:This is due to Grafana having a new ingress interface. We need to:
Tip
Breaking backwards compatability in our TF modules, e.g. upgrading an interface, also disables the use of Terraform to upgrade our product. Related:
Solution
This PR has
mainas the merge target with these changes:2/stablewith TF module sourced from?ref=track/2channel=1/stablesince we don't support a track 1 deploymenttrack/22/stabletodev/edgeChecklist
Context
Testing Instructions
The goal of this testing is to ensure that the module can fully deploy without
Client Error.COS Lite
Apply complete! Resources: 34 added, 0 changed, 0 destroyed.COS
Apply complete! Resources: 87 added, 0 changed, 0 destroyed.Upgrade Notes