-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Add a command line flag to accept all prompts to enable scripted execution #307
Comments
For AT: medic-conf has a The branch is |
This isn't a bug because the code is working as intended. Added to 3.11.0 and assigned to Nick because he's already working on it. |
Looks good with the
|
@ngaruko I'm struggling to reproduce this. Can you provide more detail about how your setup and what state your instance was in? |
Couldn't replicate. I guess we can close it off - assume I made a mistake and tested while still on |
Scripts that use medic-conf to automate deployments hang waiting on the following input:
We can't determine if you're going to overwrite someone else's changes or not. Would you like to proceed? [y/n]:
This experience is great when there is a user present but for automated scripts (travis, CI pipelines, etc) medic-conf should support an option to
--force
the deployment and--unattended
exit with an error isntead of prompting the user.One example is LG's CI pipeline. This experience is incompatible with their pipeline and will effectively block their upgrade to 3.8.1 since medic-conf 3.1 is required to work with that version of the core.
The text was updated successfully, but these errors were encountered: