Discussion: How to avoid test data being added to production for future features.
Summary
During our milestone retro sync, we discussed how we can avoid scenarios in the future where test data was added into production for CI Catalog.
Though we removed the test data and fixed the root cause via gitlab-org/gitlab!148874 (merged) and gitlab-org/gitlab!149048 (merged) so CI Catalog won't be affected in live environment data testing, we need to get to a better point where we aren't being reactive to this scenarios.
Aside from having polluted data in production, it also affects trust with our users that the features we build are legit and can be used and relied on for their purposes.