Feature: Need a feature to enable or disable the protect configuration at environment level.

[venkytek3036]

🔖 Feature description

Implement a feature to enable or disable the protect configuration at the environment level. Currently, the protect configuration is supported only at the application level. When there is a requirement to update deployment templates of the whole environment using the bulk update feature, we have to manually disable the protect configuration for each application in the environment.

🎤 Pitch / Usecases

1. Allows only super-users to enable or disable the protect configuration for the entire environment simultaneously, reducing the time and effort required for configuration changes.
2. Simplifies the process of managing protect configurations during bulk updates, ensuring that all applications in the environment can be updated consistently.
3. Providing an environment-level control for protect configurations will enhance the usability and manageability of deployment settings.
4. Reduces the risk of human error by eliminating the need to manually change settings for each application individually.

🔄️ Alternative

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

AB#10044

[abhibhaw]

This has been released @venkytek3036 @ajaydevtron please coordinate for a demo