-
Notifications
You must be signed in to change notification settings - Fork 245
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
Return object in converter if is SecretBytes #135
Conversation
Test in the JCasC PR using incremental version: jenkinsci/configuration-as-code-plugin#1282 |
exports fine, I tried every type of credential that came from installing
|
Hmmm at the same time should we try and fix that the exported things are returned as |
separate improvement 😉 **** is much better than ALL creds being skipped |
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.
Seems reasonable. Can you add any tests for this?
There's a test here: I can port it over if you want? There's a circular dependency though, the test won't pass until JCasC is fixed, which means this would need the incrementals version of JCasc to be here and JCasc needs the incrementals... |
That test looks fine, no need to port it here. |
The build is green on the jcasc side if you want to 🚢 now, (Must've keyboard mashed in between running the test locally and committing 🤕 jenkinsci/configuration-as-code-plugin@c6f4a24) |
a rebuild of this hit 1 test failure on a web client test (note it passed on the previous build):
|
Would be nice with a release 🙏 |
Partially fixes jenkinsci/configuration-as-code-plugin#1170
The other part is a null check in JCasC
Before this change, if one credential was a FileCredentialsImpl then no credentials could be exported (see the linked issue above), after this change and a null check in JCasC I can export all credentials including FileCredentialsImpl