-
Notifications
You must be signed in to change notification settings - Fork 487
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
Remove KMS requiring metadata files (closes #4375) #4700
Remove KMS requiring metadata files (closes #4375) #4700
Conversation
22f1702
to
ab8706c
Compare
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
ab8706c
to
a6957bb
Compare
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.
Thank you @keeganwitt for this contribution!
I have some concerns, related with the config name, allowing to have both the key_metadata_file
and the key_metadata
setting at the same time, and the validation of the key_metadata
value configured.
I've commented on the AWS plugin, but the same comments apply to the others. Please let me know what you think. Thanks again!
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
ece2cb2
to
58085c4
Compare
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
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.
Thank you @keeganwitt for your patience. I went over the validations that should be applied in all the cases and left a couple of comments related with that. I also have some suggestions for the documentation (I did it only for the AWS KMS case, but applies to the rest also).
We should be ready to go after this is addressed. Thanks again!
2834f6a
to
3ab3205
Compare
Co-authored-by: Agustín Martínez Fayó <amartinezfayo@gmail.com> Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
Co-authored-by: Agustín Martínez Fayó <amartinezfayo@gmail.com> Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
Co-authored-by: Agustín Martínez Fayó <amartinezfayo@gmail.com> Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
8a73374
to
8d7ad4d
Compare
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
8d7ad4d
to
fb061c0
Compare
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
bc27a92
to
e078c06
Compare
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
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 a couple of final comments:
- The
gcp_kms
plugin is missing the deprecation warning log when usingkey_metadata_file
. - Could you update
server_full.conf
with the changes?
Thanks!
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
…required Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
I think I have this already? https://github.com/spiffe/spire/pull/4700/files#diff-3dc348b71fdca86ef32e199c452c68d0bc8c70438010305d256fd94fa112ef80R1135
Done. |
I was referring that the |
Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
Ah, gotcha. Added. |
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.
🎉 Thank you @keeganwitt!
* Remove KMS requiring metadata files (closes spiffe#4375) Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
* Remove KMS requiring metadata files (closes spiffe#4375) Signed-off-by: Keegan Witt <keeganwitt@gmail.com>
Pull Request check list
Affected functionality
Removes requirement to have KMS metadata kept in files.
Description of change
Adds new config options to avoid the need to use metadata files.
Which issue this PR fixes
#4375