1 vote
Hi :)
Normally we can put an App into maintenance mode, and prevent non-admin users from accessing it during maintenance.
But we have cases where we develop in the dev/test instance of our platform, sync to git, and then the production instance pulls it (one-way sync).
So we have to put the dev version into maintenance mode aswell, which is not ideal, since our Q&A testers cant actually test anything, if we need to debug on a new issue during the maintenance.
So - please allow us to set the maintenance mode for apps, even if one-way sync is enabled - and perhaps add a checkmark, that the maintenance mode will be reverted to its Git stage settings, on the next reboot of the service.
Hi Krle,
Thank you for submitting this feature request.
I understand the use case. The current behavior appears to align with how One-Way Git Sync is designed, since the production instance pulls configuration from Git and the local Admin Console is read-only. That means changing the App maintenance state directly on production would also be treated as a local configuration change.
Your request makes sense as a feature enhancement: allowing App Maintenance Mode to be overridden locally, even when One-Way Sync is enabled, or allowing that override to reset back to the Git-defined state after the next service restart.
For now, the closest supported approach would be to manage this through separate dev/test and production branches, so the production branch can carry the production maintenance state while dev/test remains available for QA validation. I understand this does not fully cover the operational workflow you described, so I will keep this as a feature request for internal review.
Relevant documentation:
https://docs.powershelluniversal.com/config/git
Best regards,
Ruben Tapia