7eff7b51aa
* Refactors ConfirmAction implementation as a popover * Improves copy surrounding consequences of destructive actions * Moves 'Delete' buttons to Toolbar
37 lines
1.1 KiB
Handlebars
37 lines
1.1 KiB
Handlebars
<PageHeader as |p|>
|
|
<p.levelLeft>
|
|
<h1 class="title is-3">
|
|
Seal this vault
|
|
</h1>
|
|
</p.levelLeft>
|
|
</PageHeader>
|
|
|
|
{{#if model.seal.canUpdate}}
|
|
<div class="box is-sideless is-fullwidth is-marginless">
|
|
<p>
|
|
Sealing a vault tells the Vault server to stop responding to any
|
|
access operations until it is unsealed again. A sealed vault throws away
|
|
its master key to unlock the data, so it physically is blocked from
|
|
responding to operations again until the Vault is unsealed again with
|
|
the "unseal" command or via the API.
|
|
</p>
|
|
</div>
|
|
<div class="field is-grouped box is-fullwidth is-bottomless">
|
|
<ConfirmAction
|
|
@buttonClasses="button is-primary"
|
|
@confirmTitle="Seal this cluster?"
|
|
@confirmMessage="You will not be able to read or write any data until the cluster is unsealed again."
|
|
@confirmButtonText="Seal"
|
|
@horizontalPosition="auto-left"
|
|
@onConfirmAction={{action "seal"}}
|
|
data-test-seal="true"
|
|
>
|
|
Seal
|
|
</ConfirmAction>
|
|
</div>
|
|
{{else}}
|
|
<EmptyState
|
|
@title="This token does not have sufficient capabilities to seal this vault"
|
|
/>
|
|
{{/if}}
|