You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 6, 2018. It is now read-only.
Consider the following case: Someone spawns an RDS instance and accidentally exposes it publicly. We generate a violation, they fix the configuration and resolve the violation. A few months later, someone changes the same instance's configuration, exposing it once more. Then users would expect another violation of the same type to be generated. However, fullstop currently doesn't trigger if there is already a violation for that instance, even if it is a resolved one.
Step needed
Evaluate for all violation types whether it makes sense to trigger multiple violations of the same type for the same set of primary keys (such as RDS instance ID).
Implement any changes deemed necessary.
Possibly inform users.
Dependencies
None.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Expected behavior
Consider the following case: Someone spawns an RDS instance and accidentally exposes it publicly. We generate a violation, they fix the configuration and resolve the violation. A few months later, someone changes the same instance's configuration, exposing it once more. Then users would expect another violation of the same type to be generated. However, fullstop currently doesn't trigger if there is already a violation for that instance, even if it is a resolved one.
Step needed
Dependencies
None.
The text was updated successfully, but these errors were encountered: