-
Notifications
You must be signed in to change notification settings - Fork 13
Update to ACK runtime v0.56.0, code-generator v0.56.0
#61
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.
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Copilot Autofix
AI 5 days ago
The best way to fix the problem is to set an explicit
permissionsblock at the workflow or job level. Since the workflow only defines a single job that calls a reusable workflow, setting permissions at the workflow root is sufficient and ensures all jobs inherit these permissions (unless overridden). The recommended minimal starting point ispermissions: {}at the top level, which denies all by default; you can then increase permissions as needed. However, the appropriate permissions depend on the requirements of the reusable workflow being called. If unsure, start withpermissions: read-all(which is less privileged than the old default), or preferably, an empty map ({}) for no permissions.For this fix, add the following to the workflow after
name: Hydrate Go Proxyand beforeon::No imports, methods, or additional definitions are required; this is a YAML workflow modification only.