-
Notifications
You must be signed in to change notification settings - Fork 60
Update to ACK runtime v0.56.0, code-generator v0.56.0
#253
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 4 days ago
To fix the issue, we should add a
permissions:block specifying the minimal required privileges for the workflow. The best way is to add apermissions:block at the top (workflow root level), but placing it at the job level is also valid. Since the YAML shown does not indicate any specific permissions are needed for this job (and since it just delegates to a reusable workflow), start withpermissions: {}to grant no permissions at all. If it is later found that read access is required (e.g., by the reusable workflow), usepermissions: contents: read.We'll add the
permissions:block at the root level in.github/workflows/postsubmit.yaml, between thename:section and theon:section, matching the standard layout. No additional imports or configuration is needed—just the addition of the following lines: