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
Currently, we have to periodically go through and clean up resources clogging up quota because they were created instead of bootstrapped. This is a large manual effort (because it requires finding impacted tests and correcting them).
We should be able to automatically identify when specific types of resources (that should be bootstrapped) are instead being created in a test. We could then automatically alert the user to this fact. This would ideally be as an inline review comment based on the line where the resource shows up in the test file.
melinath
changed the title
Automatically detect tests that add resources that should be bootstrapped instead
Automatically when detect tests add resources that should be bootstrapped instead
Oct 10, 2024
Note that we may still want these resources to appear in examples some of the time. We may want some way to promote-to-bootstrapped within the test config, or omit resource blocks or something.
What kind of contribution is this issue about?
Pull request UX
Details
Currently, we have to periodically go through and clean up resources clogging up quota because they were created instead of bootstrapped. This is a large manual effort (because it requires finding impacted tests and correcting them).
We should be able to automatically identify when specific types of resources (that should be bootstrapped) are instead being created in a test. We could then automatically alert the user to this fact. This would ideally be as an inline review comment based on the line where the resource shows up in the test file.
References
This may require also documenting how to use bootstrapped resources and cleaning up resources that should have been bootstrapped afterwards.
The text was updated successfully, but these errors were encountered: