Conversation
ashleyyip
force-pushed
the
ashley.yip/terraform-update-tag-pipelines-new-field
branch
from
dbf5c9f to
6d45276
Compare
drichards-87
approved these changes
Feb 5, 2026
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
2 participants
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.
Motivation
In CCM's Tag Pipelines product we have a new field in the API
if_tag_exists(which accepts 3 string optionsappend,replace,do_not_apply) to replace the existingif_not_existsboolean.Changes
This PR updates the relevant resource (
tagPipelineRulesetResource) and data source (tagPipelineRulesetDataSource) to support this new field and deprecate the old field. This change applies to all rule types supported in Tag Pipelines:Tests were updated to reference the old field:
data_source_datadog_tag_pipeline_ruleset_test.goresource_datadog_tag_pipeline_rulesets_test.goresource_datadog_tag_pipeline_ruleset_test.go(I also left existing tests referencing the deprecated field to test backwards compatibility)Docs and examples are updated to reflect the new
if_tag_existsfield, as well as adding a deprecation message toif_not_exists.