Skip to content

[DOCS-13346] Update CCM Tag Pipelines docs for replace tag feature#34449

Open
rtrieu wants to merge 2 commits intomasterfrom
rtrieu/docs-13346-new-feature-replace-tag-ccm
Open

[DOCS-13346] Update CCM Tag Pipelines docs for replace tag feature#34449
rtrieu wants to merge 2 commits intomasterfrom
rtrieu/docs-13346-new-feature-replace-tag-ccm

Conversation

@rtrieu
Copy link
Contributor

@rtrieu rtrieu commented Feb 6, 2026

What does this PR do? What is the motivation?

Updates the Tag Pipelines documentation to reflect the new dropdown feature that allows users to choose whether to replace, append, or skip applying a tag when it already exists.

Merge instructions

Merge readiness:

  • Ready for merge

Additional notes

Includes a warning that the "Replace" option can overwrite existing data.

Replace the boolean "Only apply if tag doesn't exist" option with a dropdown
that offers three choices: don't apply the rule, append the tag, or replace
the tag. Add warning about the destructive nature of the replace option.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@rtrieu rtrieu requested review from a team as code owners February 6, 2026 20:27
@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

Preview links (active after the build_preview check completes)

Modified Files


Add the application tag to resources with `app`, `webapp`, or `apps` tags. The rule stops executing for each resource after the first match is found. For example, if a resource already has an `app` tag, then the rule no longer attempts to identify a `webapp` or `apps` tag.

To ensure the rule only applies if the `application` tag doesn't already exist, click the toggle in the **Additional options** section.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be updated with the new options, it works exactly the same as the "Add key" section


Under the **Additional options** section, you have the following options:

- **Only apply if columns don't exist** - Ensures the defined columns are only added if they do not already exist with the associated tags from the cost data.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same suggestion as above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants