-
Notifications
You must be signed in to change notification settings - Fork 89
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
CLI notices #308
Labels
management/tracking
status/api-approved
API Bar Raiser signed-off the API of this RFC
status/done
Implementation complete
Comments
Love this! |
Another idea: have some rule that matches resources in templates, and throws up an advisory if we find a resource that matches some pattern or rule. |
Merged
@otaviomacedo Can we mark this as done? 🎉 Edit: Whoops, I didn't notice the label |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
management/tracking
status/api-approved
API Bar Raiser signed-off the API of this RFC
status/done
Implementation complete
Description
We don't have a good way of communicating urgent matters to our users. This becomes especially relevant when security issues or breakages are discovered--we want to push communication around this, but the AWS Blog is not appropriate, Personal Health Dashboard might not get looked at and email will get spammy.
The CLI is an obvious place to integrate.
Working Backwards
The CDK CLI now automatically lets you know about issues that are important for the correctness, health and security of your CDK applications and toolchain.
Example messages we will push to you are:
package.json
, or you have carets on any of them (alternatively: you have multiple copies of the CDK in your dependency tree)Every advisory is accompanied by a link information you about the details of the advisory, and what you should do to protect yourself.
CDK will tell you about applicable advisories on every run. You can opt to ignore messages and never be notified of them again.
Roles
The text was updated successfully, but these errors were encountered: