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
I would like to be able to archive deployments. So they are not directly shown in the deployments list - only when a new filter "show archived" is added. Maybe adding a hint if a filter on the UI would match 'archived' deployments too - so there is not too much confusion on the UI when stuff disappears.
And archived deployments should not show up on the Rest API as well (if one does not add that filter there too).
The use case we have is that some applications are deployed to environments by accident. They then get deleted from the infrastructure but our auomation tools still see that deployment to be successful on that environment. With an archive feature I would be able to get that out of the way. Archive not delete because this sometimes happens on production and any deployment on production must be back-traceable (even the accidental ones).
The text was updated successfully, but these errors were encountered:
Hello
I would like to be able to archive deployments. So they are not directly shown in the deployments list - only when a new filter "show archived" is added. Maybe adding a hint if a filter on the UI would match 'archived' deployments too - so there is not too much confusion on the UI when stuff disappears.
And archived deployments should not show up on the Rest API as well (if one does not add that filter there too).
The use case we have is that some applications are deployed to environments by accident. They then get deleted from the infrastructure but our auomation tools still see that deployment to be successful on that environment. With an archive feature I would be able to get that out of the way. Archive not delete because this sometimes happens on production and any deployment on production must be back-traceable (even the accidental ones).
The text was updated successfully, but these errors were encountered: