rfc: Functions for Hinting About Unknown Values#3539
Draft
apparentlymart wants to merge 1 commit intomainfrom
Draft
rfc: Functions for Hinting About Unknown Values#3539apparentlymart wants to merge 1 commit intomainfrom
apparentlymart wants to merge 1 commit intomainfrom
Conversation
This document proposes adding some new built-in functions to the OpenTofu language to allow module authors to optionally give OpenTofu additional hints about the range of values that ought to be possible in a particular location, either to avoid an unknown value appearing in a location where the OpenTofu language disallows that, or just to make the generated plan more complete so that it's easier to review either manually or using automatic review tools. Signed-off-by: Martin Atkins <mart@degeneration.co.uk>
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
1 participant
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.
This document proposes adding some new built-in functions to the OpenTofu language to allow module authors to optionally give OpenTofu additional hints about the range of values that ought to be possible in a particular location, either to avoid an unknown value appearing in a location where the OpenTofu language disallows that, or just to make the generated plan more complete so that it's easier to review either manually or using automatic review tools.
(This is not finished yet. I intend to keep working on this at some point, but it's not my main foreground task at the moment so I've just started this draft as a placeholder.)
Related issues (some more related than others):
convertfunction for converting values to conform to specific type constraints #2630yamldecodecauses resource attribute used in count meta-argument to be unknown during plan #3533