Vault Automation 43519e1220
UI: Add ACL Policy Intro Page (#12332) (#12444)
* move policy template logic into page component and add acl policy intro page

* do not show wizard for empty state caused by filter, clean up policy page component

* add and update tests, add changelog entry

* update modal copy

* update comment

* address test failure

* Update ui/app/components/page/policies.ts



* Apply suggestions from code review



* update deletion method and add
test coverage

* update comment

* clean up

* update intro action

---------

Co-authored-by: lane-wetmore <lane.wetmore@hashicorp.com>
Co-authored-by: claire bontempo <68122737+hellobontempo@users.noreply.github.com>
2026-02-19 19:29:34 +00:00

29 lines
1.3 KiB
Handlebars

{{!
Copyright IBM Corp. 2016, 2025
SPDX-License-Identifier: BUSL-1.1
}}
<Wizard::IntroContent
@isOptional={{true}}
@setupTime="15 min"
@description="Namespaces let you create secure, isolated environments where independent teams can manage their own secrets engines, auth methods, and policies within a single Vault cluster."
@imageAlt="namespace hierarchy example"
@imageCaption="Namespaces provide necessary isolation based on your company's organization and access requirements."
@imageSrc={{img-path "~/namespaces-intro.png"}}
>
<:features>
<Wizard::IntroContent::Feature @icon="service">
Use for multi-tenancy: strict
<strong>administrative and configuration isolation</strong>
between business units and client environments.
</Wizard::IntroContent::Feature>
<Wizard::IntroContent::Feature @icon="database">
Namespaces allow you to segment your cluster into
<strong>separate logical partitions</strong>, with isolated data, policy, and tokens.
</Wizard::IntroContent::Feature>
<Wizard::IntroContent::Feature @icon="org">
Namespaces should not be used like folders. Use them for
<strong>large-scale, highly-regulated</strong>
environments.
</Wizard::IntroContent::Feature>
</:features>
</Wizard::IntroContent>