Use --env instead of --zone to start the server in development environment #2878
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Use
--env
instead of--zone
to start the server in development environment.development.yaml
is recreated as a symlink todevelopment-cass.yaml
to allow to run default server configuration without specifing--env
or--zone
params.Why?
To prevent implicit config merge behaviour.
How did you test it?
Run locally.
Potential risks
If someone manually start server with
--zone
parameter using existing development config files, it needs to be changed to use--env
instead. Production usage of manually created zone configs is not affected (still works).Is hotfix candidate?
No.