NPA-1308: Added changes to suppress computed fields in plan #264
+5,136
−3
Conversation
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
rsharmaInfoblox
changed the title
rsharmaInfoblox
requested review from
Aish-sp,
AnilGadiyarHJ,
Chaithra001,
JkhatriInfobox,
Tejashree-RS,
VishrutiBuddhadev and
unasra
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.
Added changes to suppress computed fields in plan.
This change introduces a custom
UseStateForUnknownplan modifier for all computed-only fields. The modifier currently works based on a global flag (later we can move this into a unified provider-level config structure).By default, the flag is disabled, so all computed fields will continue to appear in the plan output. Admins can enable the flag to suppress these values during planning.
Note: At the moment, the plan modifier is applied to all nested fields, even when the parent attribute is already computed. Ideally, we should avoid adding the modifier to nested fields to reduce code bloat. However, skipping it complicates generation for new objects created via Mustache templates. To maintain consistency across objects, the modifier is applied uniformly for now.