Conversation
|
|
7935ce3 to
b3a6f0c
Compare
.github/workflows/ci.yml
Outdated
| secrets: inherit | ||
| permissions: | ||
| contents: read | ||
| id-token: write |
There was a problem hiding this comment.
The permission block is not needed here: id-token: write is specified line 74, and contents: read should be defined in the policy
.github/workflows/run-exotics.yml
Outdated
|
|
||
| on: | ||
| workflow_call: | ||
| inputs: |
There was a problem hiding this comment.
it will also need a permission block with id-token: write since this workflow calls DataDog/dd-sts-action
.github/workflows/run-end-to-end.yml
Outdated
| with: | ||
| repository: 'DataDog/system-tests' | ||
| ref: ${{ steps.compute_ref.outputs.ref }} | ||
| - name: Get Datadog credentials |
There was a problem hiding this comment.
will need id-token: write permissions to invoke DataDog/dd-sts-action
| default: "datadoghq.com" | ||
| required: false | ||
| type: string | ||
| dd_sts_policy: |
There was a problem hiding this comment.
will need id-token: write permissions to invoke DataDog/dd-sts-action
7a4fc9b to
107bbb0
Compare
107bbb0 to
b4b5967
Compare
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🔗 Commit SHA: d4a2f58 | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback! |
|
@nccatoni with https://github.com/DataDog/dd-source/pull/405204 it should be possible to test your PR as a nested workflow on DataDog/dd-trace-rb |
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d4a2f58d65
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # https://docs.datadoghq.com/tests/setup/junit_xml/?tab=linux | ||
| - name: Push results | ||
| if: github.event.pull_request.user.login != 'dependabot[bot]' && inputs.datadog_api_key != '' | ||
| if: github.event.pull_request.user.login != 'dependabot[bot]' |
There was a problem hiding this comment.
Skip upload when no Datadog credentials are configured
The Push results step now runs for every non-Dependabot execution, even when both credential sources are empty. If inputs.datadog_api_key is '' and inputs.dd_sts_policy is also '', the dd-sts step is skipped and DATADOG_API_KEY resolves to an empty value, so datadog-ci junit upload is still invoked without auth and can fail the job. This is a regression from the previous guard and affects callers that enable push_to_test_optimization without passing either credential source (for example workflows that rely on system-tests.yml defaults).
Useful? React with 👍 / 👎.
Motivation
Changes
Workflow
🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist
tests/ormanifests/is modified ? I have the approval from R&P teambuild-XXX-imagelabel is present