Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should platform drush cset be run non-interactively #209

Open
andriokha opened this issue Oct 7, 2024 · 0 comments
Open

Should platform drush cset be run non-interactively #209

andriokha opened this issue Oct 7, 2024 · 0 comments

Comments

@andriokha
Copy link

Hi, I'm not sure if this is a bug or expected behavior, but it strikes me as potentially risky. I'm not being asked for confirmation when running platform drush cset. In the following example I run the same drush command twice, once via ddev affecting a local environment, and once via platform affecting the production environment. The platform version doesn't ask for confirmation and is affecting the config on production.

$ ddev drush cset config_ignore_auto.settings ignored_config_entities '[]'

 ┌ Do you want to update ignored_config_entities key in config_ignore_auto.settings config? ┐
 │ Yes                                                                                      │
 └──────────────────────────────────────────────────────────────────────────────────────────┘

$ platform drush cset config_ignore_auto.settings ignored_config_entities '[]' && echo success
success
$ env | grep -E '(PLATFORM|DRUSH)'
$ platform --version
Platform.sh CLI 5.0.22

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant