-
Notifications
You must be signed in to change notification settings - Fork 788
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
feat: support for generated secrets in schemas #4347
Conversation
pkg/util/secrets/secrets.go
Outdated
allowRepeat = true | ||
) | ||
|
||
// Generate a secret using sensible defaults |
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.
comment on exported function DefaultGenerateSecret should be of the form "DefaultGenerateSecret ..."
b5b8f31
to
b7f7583
Compare
Codecov Report
@@ Coverage Diff @@
## master #4347 +/- ##
=========================================
Coverage ? 31.17%
=========================================
Files ? 688
Lines ? 90588
Branches ? 0
=========================================
Hits ? 28243
Misses ? 60945
Partials ? 1400
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #4347 +/- ##
==========================================
- Coverage 31.18% 31.18% -0.01%
==========================================
Files 687 688 +1
Lines 90565 90585 +20
==========================================
Hits 28245 28245
- Misses 60921 60941 +20
Partials 1399 1399
Continue to review full report at Codecov.
|
b7f7583
to
28a4d7c
Compare
If `"default":"<generated>”` is used on a token or a password then it will default to a generated secret Signed-off-by: Pete Muir <pmuir@bleepbleep.org.uk>
28a4d7c
to
ccd9b67
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jstrachan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
If `"default":"<generated>”` is used on a token or a password then it will default to a generated secret Signed-off-by: Pete Muir <pmuir@bleepbleep.org.uk>
If `"default":"<generated>”` is used on a token or a password then it will default to a generated secret Signed-off-by: Pete Muir <pmuir@bleepbleep.org.uk>
If `"default":"<generated>”` is used on a token or a password then it will default to a generated secret Signed-off-by: Pete Muir <pmuir@bleepbleep.org.uk>
If `"default":"<generated>”` is used on a token or a password then it will default to a generated secret Signed-off-by: Pete Muir <pmuir@bleepbleep.org.uk>
If `"default":"<generated>”` is used on a token or a password then it will default to a generated secret Signed-off-by: Pete Muir <pmuir@bleepbleep.org.uk>
If `"default":"<generated>”` is used on a token or a password then it will default to a generated secret Signed-off-by: Pete Muir <pmuir@bleepbleep.org.uk>
…ins-x#4360) If `"default":"<generated>”` is used on a token or a password then it will default to a generated secret Signed-off-by: Pete Muir <pmuir@bleepbleep.org.uk>
Submitter checklist
Description
feat: support for generated secrets in schemas
If
"default":"<generated>”
is used on a token or a password then it will default to a generated secretSigned-off-by: Pete Muir pmuir@bleepbleep.org.uk
Special notes for the reviewer(s)
Which issue this PR fixes
#4328