Issues with Ordering When Using Vault CLI's -no-print Argument

Today I've been fighting a bit of an issue with the Vault CLI (v1.1.2) not masking the output of a vault login.

It appears that this is due to the ordering of the arguments I was using:

-vault login -method=aws -path=aws-ec2 role=.... -no-print=true
+vault login -no-print=true -method=aws -path=aws-ec2 role=....

In the former command, it appears that the EC2 auth takes arguments (i.e. role) which are slightly different to Vault's usual arguments, such as -no-print.

By moving it earlier in the command, it no longer prints output for the result of login.

Written by Jamie Tanna's profile image Jamie Tanna on , and last updated on .

Content for this article is shared under the terms of the Creative Commons Attribution Non Commercial Share Alike 4.0 International, and code is shared under the Apache License 2.0.

#blogumentation #vault #aws.

This post was filed under articles.

Related Posts

Other posts you may be interested in:

Interactions with this post

Interactions with this post

Below you can find the interactions that this page has had using WebMention.

Have you written a response to this post? Let me know the URL:

Do you not have a website set up with WebMention capabilities? You can use Comment Parade.