-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
UI: PKI Generate Root Form #18712
UI: PKI Generate Root Form #18712
Conversation
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.
Nice work on this! This form is a doozy. Holding off approving until tests pass, and we've confirmed the expected key parameters functionality
@model={{this.model}} | ||
@onCancel={{transition-to "vault.cluster.secrets.backend.pki.issuers.index"}} | ||
@onSave={{transition-to "vault.cluster.secrets.backend.pki.issuers.index"}} |
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.
Would saving take us to the generated root cert?
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.
I used to have a note about parsing the issuer from the save response and passing that for the onSave transition. I plan on looking into that with the generate-csr work -- for now, I figured this is a reasonable if not ideal transition
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.
Yeesh - the pki workflow flow 🤯. Yeah, sounds more than reasonable!
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.
really great work on this 🥇
I was wrong about your changes to the pki-key-paremeters
component (yay - tests worked!?) It didn't affect the functionality of the form to generate a key 💯.
Sorry about the mis-comment!
this.showGroup = isOpen ? group : null; | ||
} | ||
|
||
get defaultFields() { |
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.
Having a component getter makes this so much clearer. Instead of passing a huge array of objects with arrays of attrs as groupPropertyNames
to the model decorator (like we did in pki/roles)
This PR adds a new component in the PKI engine,
PkiGenerateRoot
. It also renames the model/adapter/serializerpki/config
topki/action
to better represent that the actions it encompasses can happen in places other than initial PKI configuration.Form is rendered on config if Generate Root is selected
Form is rendered from issuers > generate root selection
Follow-on tasks:
pki/action
serializerpki-key-parameters