Action Requested: App Configuration Problems Found in repo [copilot-runtime-bazel-cache]
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
What is this?
In order to help ensure a smooth and painless deployment experience, we scan each repository for potential configuration problems. Our scanner has identified some problems with copilot-runtime-bazel-cache's configuration which might cause unexpected application behavior. These issues were found on copilot-runtime-bazel-cache's default branch during the last linter run.
NOTE: moda-linter validates configurations for all repos regardless of deployment strategy.
What do I need to do?
- Review the list of problems below.
- Fix the problems listed by correcting the problem or adding an ignore rule. There are links on each item for more information on how to do so.
- Verify the fix by opening a new PR. The linter will automatically run and annotate any remaining problems on your PR. If your fixes are correct, you should not see any new annotations.
- Once the fixes have been merged, feel free to close this issue.
Does a rule not apply to your configuration? False positives?
We are aware of certain exceptions to our rules, but our bot is not. If you would like to ignore a rule, please see the following documentation: Ignoring Rules.
Please be certain that you need to ignore a rule before doing so. These checks are here to help prevent hard-to-debug deployment issues, lighten the burden on the support team, and ultimately make the deployment process smoother.
What happens now?
This check will run on a regular interval. If we detect configuration problems in copilot-runtime-bazel-cache's default branch, this issue will be reopened.
Help!
Each rule includes a link to documentation explaining the violation and how to fix it. If you still have questions after reading the docs, please use the owning team and Slack contact information included with that violation in the list below.
The linter framework is maintained by #dx-pathfinders.
Detected Configuration Problems
| Issue | File | More Info |
|---|---|---|
| kube-validation#deployments without readiness probe | deployment.yaml | Deployment copilot-runtime-bazel-cache has a container metrics-proxy without a readinessProbe More info: https://github.com/github/moda-linter/blob/main/rules/docs/deployments_without_readiness_probe.md Reach out to #dx-pathfinders for assistance. This rule is owned by: @github/dx-pathfinders |
| kube-validation#splunk index exists | deployment.yaml | Deployment copilot-runtime-bazel-cache is specifying a nonexistent splunk index as destination for its logs More info: https://github.com/github/moda-linter/blob/main/rules/docs/splunk_index_exists.md Reach out to #splunk for assistance. This rule is owned by: @github/platform-fundamentals |
cc @github/copilot-cli
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with config/kubernetes/production/deployments/deployment.yaml at the reported lines, then read the linked moda-linter documentation for deployments without readiness probes and nonexistent Splunk indexes. Review the metrics-proxy container and the configured logging destination, and verify the changes by opening a PR and confirming that the linter reports no remaining annotations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100