Rewrite terraform app config to be chunk-aware#123
Merged
Conversation
e4b2a84 to
569de3d
Compare
Merged
jnu
added a commit
that referenced
this pull request
Mar 31, 2025
Follow up to #123 and #124 to fully deprecate `latest` channel. This means we will *not* push to `latest` anymore. Untested updates will go to `unstable` and official version bumps will go to `stable`. Doing this now has the convenient property of preventing a regression from unintended image updates without a corresponding terraform update (as noted in #123).
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.
Rewrites the app config in Terraform to account for output window constraints in the parse and redact/inspect steps and apply a limited amount of iteration when truncation is detected.
By default the config will attempt up to 5 iterations to complete the specified task. This limit can be increased by editing the
{redact,parse}_chunks_max_iterationsvariables in the Terraform variables file.Since this PR relies on the rewritten experimental chunking support that's been available in the app for several weeks, deploying this new Terraform change should not result in any new functions. There will, however, be a regression (turning chunking support off) if a new API image is deployed without running the terraform update.