Want way to designate ICD resources as 'non-prod' (vs. 'prod') so that when deprecation of older versioned resources occur (like Rabbit 3.9 happening today on Sept 21st), the 'non-prod' flagged resources can be deprecated a week or two earlier. This way, if a team does not address the deprecation in time (sometimes due to devops guy being 'resource action'ed), only the 'non-prod' environments go down and the development/maintenance teams will then be aware of the transition required in production in the next week or two.
| Idea priority | Medium |
| Needed By | Not sure -- Just thought it was cool |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.