-
Notifications
You must be signed in to change notification settings - Fork 135
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
fix(signing):Set signing keys to never expire #2004
Conversation
The ansible-sign.key also needs to be updated in clowd-app.yaml by base64 encoding the file with |
No-Issue
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.
Fixes Error creating signature: Unusable secret key
error in logs from expired key
@drodowic I updated the clowder file |
LGTM |
Backport to stable-4.6: 💚 backport PR created✅ Backport PR branch: Backported as #2005 🤖 @patchback |
No-Issue (cherry picked from commit 141ae4f)
Backport to stable-4.7: 💚 backport PR created✅ Backport PR branch: Backported as #2006 🤖 @patchback |
No-Issue (cherry picked from commit 141ae4f)
Backport to stable-4.8: 💚 backport PR created✅ Backport PR branch: Backported as #2007 🤖 @patchback |
No-Issue (cherry picked from commit 141ae4f)
Backport to stable-4.9: 💚 backport PR created✅ Backport PR branch: Backported as #2008 🤖 @patchback |
No-Issue (cherry picked from commit 141ae4f)
…s to never expire (#2007) fix(signing):Set signing keys to never expire (#2004) No-Issue (cherry picked from commit 141ae4f) Co-authored-by: Bruno Rocha <[email protected]>
…s to never expire (#2006) fix(signing):Set signing keys to never expire (#2004) No-Issue (cherry picked from commit 141ae4f) Co-authored-by: Bruno Rocha <[email protected]>
…s to never expire (#2008) fix(signing):Set signing keys to never expire (#2004) No-Issue (cherry picked from commit 141ae4f) Co-authored-by: Bruno Rocha <[email protected]>
Edited keys to never expire
No-Issue
For reference
Reexport