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

Remove Plugin from detailed output #5797

Closed
wants to merge 1 commit into from
Closed

Conversation

catsby
Copy link
Contributor

@catsby catsby commented Nov 15, 2018

Remove Plugin from the output of secrets list --detailed, which was removed in #5536

@tyrannosaurus-becks
Copy link
Contributor

@catsby good find! This makes me realize the following place would need the same:

@briankassouf
Copy link
Contributor

So this breaks bc with older versions of vault, and i think 1.0 could still return a mount with plugin_name defined. I think instead we should dynamically add the column if any of the mounts have a value set for plugin_name

@jefferai
Copy link
Member

TBH I'd go the other way -- now that everything is a plugin, we should instead add this back from #5536 and always output the plugin being used, which I believe may actually be different from the type in some cases due to plugin_name. My $0.02.

@catsby
Copy link
Contributor Author

catsby commented Nov 16, 2018

I agree with Jeff, it seems that Plugin is more relevant now that everything is a plugin

@tyrannosaurus-becks
Copy link
Contributor

@catsby @jefferai #5807

@calvn
Copy link
Contributor

calvn commented Nov 16, 2018

Couldn't we have the "Type" return the plugin name instead?

Pre-1.0.0:

# vault secrets list -detailed (partial result)
Type     Plugin 
----     ------
plugin   gen

1.0.0:

# vault secrets list -detailed (partial result)
Type    
----    
gen

@tyrannosaurus-becks
Copy link
Contributor

@calvn I believe your comment is addressed in #5825

@briankassouf
Copy link
Contributor

superseded by #5825

@briankassouf briankassouf deleted the secrets-detailed-output branch November 20, 2018 17:49
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.

5 participants