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

Run force-unlock with -no-color flag #270

Merged
merged 1 commit into from
Aug 19, 2022
Merged

Run force-unlock with -no-color flag #270

merged 1 commit into from
Aug 19, 2022

Conversation

HadrienPatte
Copy link
Contributor

This adds the -no-color flag by default to the force-unlock command.

Without this patch we can get ForceUnlock error:

exit status 1
�[31mFailed to unlock state: Lock ID should be numerical value, got 'ID'�[0m�[0m

With this patch the error becomes:

exit status 1
Failed to unlock state: Lock ID should be numerical value, got 'ID'

(I purposefully ran ForceUnlock with an invalid argument here to have it error out)

@hashicorp-cla
Copy link

hashicorp-cla commented Mar 12, 2022

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@kmoe kmoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I'm going to follow up with some tests, and will merge this PR when they are ready.

@kmoe kmoe mentioned this pull request Aug 19, 2022
@kmoe kmoe merged commit 28ec186 into hashicorp:main Aug 19, 2022
@HadrienPatte HadrienPatte deleted the force-unlock-no-color branch August 22, 2022 11:44
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

Successfully merging this pull request may close these issues.

3 participants