As a developer, I want to assign set 3 values to a single Site Property for all environments. This will dramatically speed up a deployment, where you won't browse several modules and change Site Properties depended on Environment.
It is common practice when we set a Site Property value to production value by default, and change it manually in Dev and Test. In this case we kind of avoid a "human error" if we forget it during deployment. But sometimes we have several such properties, e.g. SomeDomainUrl, which should be different for each environment.
I would suggest to inherit the practice we use in not low code:
we might have several configuration files for each environment, e.g.:
- appsettings.json
- appsettings.development.json
- appsettings.test.json
That means during a deployment build process the compiler will choose corresponding settings.
How I see it:
When you add a new Site Property, you can add (+) two more for tst and prod. If a developer does not add it, they are the same by default. Like that:
Site Property: fromEmailAddress
- Value: "noreply-dev@mydomain.com"
- (+) tst Value: "noreply-tst@mydomain.com"
- (+) prod Value: "noreply@mydomain.com"