-
Notifications
You must be signed in to change notification settings - Fork 44
Update to ACK runtime v0.56.0, code-generator v0.56.0
#188
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 3 days ago
To fix the problem, add a
permissionsblock at the top-level of the workflow in.github/workflows/postsubmit.yaml. This will ensure that all jobs, including those executing a reusable workflow via theuses:key, inherit these restrictions and do not default to broad repository permissions. Since it's unclear what minimal permissions are necessary for the called workflow, the generally safest starting point iscontents: read, which grants the ability to read repository contents but not write, unless specific additional access is required (such as for pull requests, issues, etc.). The change should be made immediately below thename:field or above theon:field, according to typical YAML conventions for GitHub Actions workflows.