Skip to content
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

Add default to allowed values for algorithm_signer #17894

Merged
merged 2 commits into from
Feb 9, 2023

Conversation

bluestealth
Copy link
Contributor

Copy link
Contributor

@hellobontempo hellobontempo left a comment

Choose a reason for hiding this comment

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

Our design team got back to me and requested that this be a dropdown select instead!

in role-ssh.js could you add possibleValues to the attribute

@cipherboy - if you want to confirm I got these right?

  algorithmSigner: attr('string', {
    helpText: 'When supplied, this value specifies a signing algorithm for the key',
    possibleValues: ['', 'default', 'ssh-rsa', 'rsa-sha2-256', 'rsa-sha2-512']
    
  }),

@cipherboy
Copy link
Contributor

@hellobontempo -- the last one should have a - rather than an = sign, but yes, LGTM :-)

@hellobontempo
Copy link
Contributor

@hellobontempo -- the last one should have a - rather than an = sign, but yes, LGTM :-)

whoops - typo! thanks :)

@@ -120,6 +120,7 @@ export default Model.extend({
}),
algorithmSigner: attr('string', {
helpText: 'When supplied, this value specifies a signing algorithm for the key',
possibleValues: ['', 'default', 'ssh-rsa', 'rsa-sha2-256', 'rsa-sha2-512'],
Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for the swift change!

Reviewing #14006 - since an empty string updates to default can we remove that from the array of possibleValues here? My apologies for the rigamarole, I noticed this while testing. It's slightly awkward UX to select nothing from the dropdown and then after saving have it magically change to "Signing Algorithm: default"

form

Screen Shot 2022-11-11 at 1 49 23 PM

config

Screen Shot 2022-11-11 at 1 49 39 PM

@cipherboy - not sure if you have an argument to keep it as a dropdown option? If so, then we can remove line 123 all together if the options are going to be the same as the backend as the dropdown complies automagically when
AllowedValues exist

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@hellobontempo that actually makes a lot of sense, made that change.

Copy link
Contributor

@hellobontempo hellobontempo left a comment

Choose a reason for hiding this comment

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

:shipit: thank you!

@hellobontempo hellobontempo added this to the 1.13.0-rc1 milestone Feb 8, 2023
@hellobontempo
Copy link
Contributor

@cipherboy Do you know how to get the Vercel status check to run here?

@cipherboy
Copy link
Contributor

@hellobontempo I don't think Vercel is holding this one up, I think completed-successfully is, but we might be able to get someone to admin merge it. But no, apparently I can no longer manage Vercel jobs... Uh-oh.

@hellobontempo
Copy link
Contributor

@hellobontempo I don't think Vercel is holding this one up, I think completed-successfully is, but we might be able to get someone to admin merge it. But no, apparently I can no longer manage Vercel jobs... Uh-oh.

Oh, I didn't even see that one. Can someone in your channel admin merge? Or should I post elsewhere?

@ncabatoff ncabatoff merged commit 0bacc16 into hashicorp:main Feb 9, 2023
@bluestealth bluestealth deleted the default-signer branch February 11, 2023 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants