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
We use a deny sync window to be able to deploy applications to the prod environment only during the maintenance window. Everything works well, however, we found that the deny sync window does not block the delete operation. It turns out that it is possible to remove all apps from the prod environment accidentally. (we have already had a bug on the gitlab side + applicationset controller that removes everything from the prod env.)
Motivation
We can update/delete applications by mistake during deny sync window. That is why, I want to be sure that all application operations (sync, create, update, delete) will be performed only during allow sync window aka the maintenance window.
Proposal
Add the ability to set what application operations will be blocked during deny sync window. or just allow any application modifications only during allow sync window.
The text was updated successfully, but these errors were encountered:
Summary
We use a deny sync window to be able to deploy applications to the prod environment only during the maintenance window. Everything works well, however, we found that the deny sync window does not block the delete operation. It turns out that it is possible to remove all apps from the prod environment accidentally. (we have already had a bug on the gitlab side + applicationset controller that removes everything from the prod env.)
Motivation
We can update/delete applications by mistake during deny sync window. That is why, I want to be sure that all application operations (sync, create, update, delete) will be performed only during allow sync window aka the maintenance window.
Proposal
Add the ability to set what application operations will be blocked during deny sync window. or just allow any application modifications only during allow sync window.
The text was updated successfully, but these errors were encountered: