Preserve null tags if not configured to prevent apply errors#8
Merged
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 pull request updates the logic for mapping tags in the
AppResourceto better handle cases where tags are not configured by the user. The main change ensures that if thetagsfield is null in the configuration, it remains null in the model, which helps prevent "inconsistent result after apply" errors.Improvements to tag mapping logic:
mapAppToModelfunction inresource_app.goto only update theTagsfield if it was configured by the user, preservingnullwhen tags are not set in the configuration. This avoids potential state drift and apply errors. [1] [2]