Skip to content
This repository has been archived by the owner on Mar 27, 2019. It is now read-only.

[Feature] Implement mountpoint management #62

Merged
merged 2 commits into from
Mar 2, 2017

Conversation

msessa
Copy link
Collaborator

@msessa msessa commented Feb 26, 2017

This PR adds mountpoint management to vault-ui.

Features:

  • Mounting of supported Auth/Secret backends
  • Tuning Auth/Secret backends default/max lease TTL
  • Unmounting Auth/Secret bakends

Functionalities can be accessed via the left side menu.
The plus icon opens a new dialog to mount backends
The wrench icon opens a new dialog to tune mountpoint parameters and delete the

Matteo Sessa added 2 commits February 26, 2017 14:40
First commit mountpoint tuning feature

Delete mountpoint feature

remove debug logs

App state fix

Mount new backend feature

Fix merge conflict
@djenriquez
Copy link
Owner

Nice work @msessa-cotd. I'll take a look in a few hours.

Copy link
Owner

@djenriquez djenriquez left a comment

Choose a reason for hiding this comment

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

Token change below, otherwise LGTM.

Also the formatter on my IDE (VS Code) wants to add spaces everywhere, are you using a formatter/linter?

>
{_.map(this.props.supportedBackendTypes, (b) => {
return (<MenuItem value={b} primaryText={b} />)
})}
Copy link
Owner

@djenriquez djenriquez Feb 28, 2017

Choose a reason for hiding this comment

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

Doesn't look like token types can be mounted:

{
    _.map(this.props.supportedBackendTypes, (b) => {
        if (b !== 'token') {
            return (<MenuItem value={b} primaryText={b} />)
        }
    })
}

@djenriquez
Copy link
Owner

@msessa-cotd theres one thing that scares me with this feature: Its too easy to delete things.

Yes, I understand there is a confirmation window so maybe i'm being paranoid, but it just seems too easy...thoughts?

@djenriquez
Copy link
Owner

I'm just picturing someone somewhere accidentally deleting the "secret/" mount even after the confirmation, and kaboom, everything is gone.

@msessa
Copy link
Collaborator Author

msessa commented Feb 28, 2017

I wouldn't worry too much. The delete button is already nested in the tune dialog, plus the delete confirmation is forced. All this on top of the fact that a user would need delete capabilities on the path (sys/mounts/generic not simply generic/) which is something the system administrator should prevent using policies.

I don't believe it's vault-ui responsibility to make up for poorly configured vaults

Copy link
Owner

@djenriquez djenriquez left a comment

Choose a reason for hiding this comment

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

Yea, great points. LGTM!

@msessa msessa merged commit f483b4b into master Mar 2, 2017
@msessa msessa deleted the feature/mountpoint_management branch March 2, 2017 07:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants