[ECR] [request]: Repository configuration defaults
<!--- Please keep this note for the community ---> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!--- Thank you for keeping this note for the community ---> **Tell us about your request** Repository configuration defaults (e.g. Turn on scan-on-push by default) **Which service(s) is this request for?** ECR **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** Since ECR scan on push was announced, customers have been asking their internal teams to enable this feature for new and existing repos, and realizing there are hundreds of opportunities to turn this on, but lacking a good way to guide teams to do this automatically going forward. Could this be an option, to turn on scan-on-push by default? **Are you currently working around this issue?** Can think of a periodic lambda, but not an ideal solution.
Posted by anupwarrier on Mar 17, 2020, 12:48 AM
Tags
Related issues
- [Meta] Feedback on granular control over Copilot changes
- unexpected status 401 Unauthorized issue
- [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
- [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
- Video stops playing after some minutes
- [MODEL] Claude verbose code comments by default — ignores instructions to stop.
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
github (Software)
[Meta] Feedback on granular control over Copilot changes
unexpected status 401 Unauthorized issue
[MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
[CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
Video stops playing after some minutes
[MODEL] Claude verbose code comments by default — ignores instructions to stop.
Scope Codex VS Code chats to the current workspace/project
Update on "Co-authored-by: Copilot" in commit messages
[ECR] [request]: Repository configuration defaults
<!--- Please keep this note for the community ---> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!--- Thank you for keeping this note for the community ---> **Tell us about your request** Repository configuration defaults (e.g. Turn on scan-on-push by default) **Which service(s) is this request for?** ECR **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** Since ECR scan on push was announced, customers have been asking their internal teams to enable this feature for new and existing repos, and realizing there are hundreds of opportunities to turn this on, but lacking a good way to guide teams to do this automatically going forward. Could this be an option, to turn on scan-on-push by default? **Are you currently working around this issue?** Can think of a periodic lambda, but not an ideal solution.
Comments (0)
No comments yet. Start the discussion.