-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Hackweek 2025 Policy Wizard #31375
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
base: main
Are you sure you want to change the base?
Hackweek 2025 Policy Wizard #31375
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
CI Results: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💣 just deleted everything that was breaking SuperSelect
in the flyout 🙃
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maps route to API paths
}; | ||
|
||
// Regex-based route matching - more flexible for parent/child relationships | ||
const ROUTE_PATTERNS: Array<{ pattern: RegExp; paths: ReturnType<typeof apiPath>[] }> = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this is one way to do this, I think it would be better and less effort to plug this into the existing capabilities service instead. That already handles permissions requests for various views. We could cache the requested paths and use those to map a route to a view instead of manually mapping route to api paths.
Description
Policy wizard to help build a policy depending on the current context of the UI.
The functionality of this POC is limited to just
secrets
but could be extended to support other routes.For example, when a user navigates to view a KV v2 secret, the fly out pre-fills the relevant paths for that view.

When capabilities are selected, it builds the policy stanza for that path:


The policy can also be assigned to various identity entities or groups:

Once selections are made, the UI can manually apply the policy or a CLI and TFVP (Terraform Vault Provider) snippet are generated that can be used depending on the users workflow.
