-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Backport 1.17.x: add allow_empty_principals to ssh engine (fixes failing test) #28493
Conversation
Build Results: |
CI Results: |
@codemirrorUpdated={{action "codemirrorUpdated" attr.name}} | ||
/> | ||
{{/each}} | ||
{{#let (find-by "name" "publicKey" this.model.attrs) as |attr|}} |
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.
@codemirrorUpdated={{action "codemirrorUpdated" attr.name}} | ||
/> | ||
{{/each}} | ||
{{#let (find-by "name" "publicKey" this.model.attrs) as |attr|}} |
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.
@@ -122,6 +123,10 @@ export default Model.extend({ | |||
helpText: | |||
'Specifies if host certificates that are requested are allowed to be subdomains of those listed in Allowed Domains', | |||
}), | |||
allowEmptyPrincipals: attr('boolean', { |
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.
Description
Manual backport of #28484
#28466 Added allow_empty_principals to the ssh engine. Though it's recommended to keep this value false we've added for parity with the backend. Also, an acceptance test was failing because a valid_principals was not provided and is now required.
TODO only if you're a HashiCorp employee
to N, N-1, and N-2, using the
backport/ent/x.x.x+ent
labels. If this PR is in the CE repo, you should only backport to N, using thebackport/x.x.x
label, not the enterprise labels.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.