-
Notifications
You must be signed in to change notification settings - Fork 1.2k
added a reminder to configure the datadog provider with the site api url #30585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added a reminder to configure the datadog provider with the site api url #30585
Conversation
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
Preview links (active after the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some feedback.
Co-authored-by: May Lee <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MassimoSporchia is this good to merge?
Yes! Thank for the review |
@maycmlee I didn't see that this change messed up the previously existing bullet point structure: https://docs.datadoghq.com/integrations/guide/aws-terraform-setup/ |
@MassimoSporchia thanks for catching that! I opened a PR to put the note in a separate bullet point: #30686 |
What does this PR do? What is the motivation?
I added a reminder on the integration page (only on the EU, if approved it would need to be propagated to other pages) to configure the terraform provider to point to the correct api_url.
We make no mention of it anywhere (e.g. this page https://docs.datadoghq.com/integrations/terraform/#troubleshooting ) has no site-specific configuration and I had customers got hit with a 403 with no troubleshooting steps to help them either.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes