-
Notifications
You must be signed in to change notification settings - Fork 41
Update to ACK runtime v0.56.0, code-generator v0.56.0
#199
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| name: Hydrate Go Proxy | ||
|
|
||
| on: | ||
| push: | ||
| branches: | ||
| - main | ||
|
|
||
| jobs: | ||
| call-hydrate-go-proxy: | ||
| uses: aws-controllers-k8s/.github/.github/workflows/reusable-postsubmit.yaml@main | ||
Large diffs are not rendered by default.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Copilot Autofix
AI 13 days ago
To fix this problem, add an explicit
permissionssection to the workflow. This can be done at the root of the workflow file (which applies to all jobs unless overridden), or at the job level for the specific job. Placing it at the root is the best approach, ensuring no job can inadvertently escalate permissions unless intentionally specified. For most workflows, especially those that just call other workflows or perform read-only actions, the recommended minimum iscontents: read. If the workflow requires write permissions for particular resources (e.g., for updating pull requests or issues), these should be added specifically. Here, as a minimal and safe starting point, add at the root:This should be inserted after the
name(line 1), before theon:trigger, so that it clearly applies to all jobs.