Add CI job to upload endpoint catalog CSV to S3#2346
Merged
Conversation
🎉 All green!🧪 All tests passed 🔗 Commit SHA: afc13e8 | Docs | Datadog PR Page | Give us feedback! |
GabrielAnca
changed the title
GabrielAnca
force-pushed
the
gabriel.anca/add-catalog-endpoints-s3-upload
branch
3 times, most recently
from
June 12, 2026 08:44
029149e to
41ce6d5
Compare
GabrielAnca
force-pushed
the
gabriel.anca/add-catalog-endpoints-s3-upload
branch
from
June 12, 2026 08:45
41ce6d5 to
afc13e8
Compare
GabrielAnca
marked this pull request as ready for review
June 12, 2026 10:00
Drarig29
approved these changes
Jun 12, 2026
Merged
GabrielAnca
added
the
datadog-ci
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.
Adds a GitLab CI job that runs on every push to master, generates the endpoint catalog CSV via
yarn catalog-endpoints, and uploads it to thedd-datadog-ciS3 bucket using CI Identities for AWS authentication.The job uses
runner:docker(legacy EC2 runner) rather thanarch:amd64(Kubernetes). On Kubernetes, the CI Identities client communicates with the signer via Fabric DNS, which uses Datadog's private PKI — a public image likenode:22doesn't carry those CA certs and would fail TLS verification. Onrunner:docker, the client uses Vault instead, which uses a publicly trusted cert. The EC2 instance profile (ci-datadog-ci, provisioned vialegacy-role: true) also provides the bootstrap credentials needed to download the CI Identities client binary from S3 beforeassume-roleis called.