Get the environment from config.yml if available #215
Merged
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.
I am having a little problem when running commands on a dev environment.
I followed the instruction in https://hechoendrupal.gitbooks.io/drupal-console/content/en/commands/settings-set.html and run
drupal settings:set environment dev
When I view the contents of ~/.console/config.yml I see:
When I run
drupal settings:debug
I get
So far, so good, but when I am on a dev environment, I would like all the commands to assume the --env option as dev, as per config. Likewise, if I am on stage, the default option should be that.
I have made a little change, to pull the settings from from config.
That should change the default option to whatever environment we are.
We still can override the environment by passing the --env option.
If there is no config, it will assume
prod
as it was before this PR.I hope what I am suggesting makes sense.