-
Notifications
You must be signed in to change notification settings - Fork 2
Creating secret.yml for github-well-architected #47
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,30 @@ | ||||||
| --- | ||||||
| secrets: | ||||||
| COPILOT_API_URL: | ||||||
| key: COPILOT_API_URL | ||||||
| type: | ||||||
| owner: | ||||||
| playbook: '' | ||||||
| externally_usable: | ||||||
| kind: latest_at_deployment_start | ||||||
| CSE_COPILOT_HMAC_KEY: | ||||||
| key: CSE_COPILOT_HMAC_KEY | ||||||
| type: HMAC | ||||||
| owner: "@github/customer-success-engineering" | ||||||
| playbook: https://github.com/github/trust-metadata-api/blob/main/docs/playbooks/rotate-hmac-keys.md | ||||||
| externally_usable: true | ||||||
| kind: latest_at_deployment_start | ||||||
| CSE_COPILOT_SERVICE_URL: | ||||||
| key: CSE_COPILOT_SERVICE_URL | ||||||
| type: | ||||||
| owner: | ||||||
| playbook: '' | ||||||
| externally_usable: | ||||||
| kind: latest_at_deployment_start | ||||||
| kittens: | ||||||
| key: kittens | ||||||
| type: kittens | ||||||
| owner: '' | ||||||
| playbook: | ||||||
|
||||||
| playbook: | |
| playbook: '' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
COPILOT_API_URLhas empty required metadata fields (type,owner, andexternally_usable). Please either settypeto an appropriate value (e.g.,configif it’s just configuration) and then omit the non-applicable keys, or fill in all required fields with valid values so this entry passes schema/lint validation.This issue also appears in the following locations of the same file: