This is in reference to the settings that are stored on the production class and cannot be put in default settings.
These are Pool Size, Enabled, Log Trace Events
As an example, there are many business hosts that are enabled on Live regarding alerting, which we do not want to have on in UAT.
On dev, a pool size of 1 will be sufficient for something and the dev environment has a very small spec computer behind it.
On prod you want a pool size of 30 for example, and it is backed by 32 cores and 128GB of RAM.
This prevents us from deploying the production file as it looks on dev to Live. This also breaks the CI/CD concepts of containerisation, where settings should be the only difference between environments.
Thank you for submitting the idea. The status has been changed to "Future consideration".
Stay tuned!
