[SEC-27541] Restrict CSM Jira issues page to GovCloud only#34973
Merged
FredMoster merged 1 commit intomasterfrom Mar 6, 2026
Merged
[SEC-27541] Restrict CSM Jira issues page to GovCloud only#34973FredMoster merged 1 commit intomasterfrom
FredMoster merged 1 commit intomasterfrom
Conversation
Contributor
2ce999c to
54cceb3
Compare
nsahifa
reviewed
Mar 4, 2026
content/ja/security/cloud_security_management/misconfigurations/kspm.md
Outdated
Show resolved
Hide resolved
nsahifa
reviewed
Mar 4, 2026
config/_default/params.yaml
Outdated
| getting_started_feature_flags: [gov] | ||
| gcp-private-service-connect: [us,us3,gov,ap1,ap2] | ||
| google-hangouts-chat: [gov] | ||
| csm_jira: [us,us3,us5,eu,ap1,ap2] |
There was a problem hiding this comment.
I’m curious how this is going to be reflected in the doc since docs.datadoghq.com isn’t per DC
Contributor
Author
nsahifa
approved these changes
Mar 4, 2026
54cceb3 to
1b6bc39
Compare
- Add csm_jira to unsupported_sites in params.yaml marking all non-gov sites as unsupported - Add site_support_id: csm_jira to jira.md front matter to trigger the unsupported banner - Remove Create Jira Issues entry from sidebar nav - Remove nextlink to Jira page from review_remediate/_index.md Rationale: The feature is being deprecated on all Datadog sites except GovCloud (us1.fed); non-GovCloud users visiting the URL directly will see an alert banner, while GovCloud users see the page normally. This commit made by [/dd:git:commit:quick](https://github.com/DataDog/claude-marketplace/tree/main/dd/commands/git/commit/quick.md)
1b6bc39 to
f256d89
Compare
buraizu
approved these changes
Mar 5, 2026
jhgilbert
approved these changes
Mar 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
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.

What does this PR do? What is the motivation?
SEC-27541
The "Create Jira Issues for Cloud Security Issues" feature is deprecated on all Datadog sites except GovCloud (US1-FED / ddog-gov.com). This PR restricts the page accordingly:
csm_jira: [us,us3,us5,eu,ap1,ap2]to theunsupported_sitesmap inparams.yaml, so the site-support banner system recognizes the feature as unsupported on non-GovCloud sites.site_support_id: csm_jirato the page front matter, causing a red alert banner to render for non-GovCloud users who visit the URL directly.nextlinkto the Jira page from thereview_remediate/_index.mdparent page.GovCloud users are unaffected: the page renders normally with no banner, as
govis not in the unsupported list.Merge instructions
Merge readiness:
Additional notes
Verification:
/security/cloud_security_management/review_remediate/— "Create Jira Issues" should not appear in the sidebar nav or the whatsnext links./security/cloud_security_management/review_remediate/jiradirectly:US1-FED→ no banner, page content displays normally.