Skip to content

Fix functions:secrets:set - stop erroring in non-interactive flows without force option #7467

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.

Sign up for GitHub

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

Jump to bottom
Merged
colerogers merged 8 commits into from
Jul 30, 2024
Merged

Fix functions:secrets:set - stop erroring in non-interactive flows without force option #7467

colerogers merged 8 commits into from
Jul 30, 2024

Conversation

@colerogers
Copy link
Contributor

@colerogers colerogers commented Jul 18, 2024 •
edited
Loading

Fixes #7466
@colerogers colerogers changed the title Adding error for non-interactive flows without force option Fix functions:secrets:set - add error for non-interactive flows without force option Jul 18, 2024
@colerogers colerogers requested review from aalej and taeold July 18, 2024 19:58
@ytetsuro
Copy link

ytetsuro commented Jul 22, 2024

@colerogers

Thank you.
If this PR is merge, it would be difficult to overwrite the secret manager value and terminate successfully without running redeploy.
Am I correct in my understanding?
I would rather not redeploy as I want to deploy stably.
joehan
joehan reviewed Jul 23, 2024
View reviewed changes
@colerogers colerogers changed the title Fix functions:secrets:set - add error for non-interactive flows without force option Fix functions:secrets:set - stop erroring in the non-interactive flows without force option Jul 30, 2024
@colerogers colerogers changed the title Fix functions:secrets:set - stop erroring in the non-interactive flows without force option Fix functions:secrets:set - stop erroring in non-interactive flows without force option Jul 30, 2024
@colerogers colerogers enabled auto-merge (squash) July 30, 2024 19:14
@colerogers
Copy link
Contributor Author

colerogers commented Jul 30, 2024

@ytetsuro I think I understand the issue better, our behavior for running functions:secrets:set with responding no to the prompt was different than running functions:secrets:set --non-interactive. The latter was producing an error that the former was not. This PR should now fix that.
@colerogers colerogers merged commit 68be9c5 into master Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants

@colerogers @ytetsuro @joehan