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
[match] propagate keychain when installing wwdr certificates #21578
[match] propagate keychain when installing wwdr certificates #21578
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
4aedf33
to
5dad6a5
Compare
5dad6a5
to
f065e6d
Compare
conflicts resolved, the CI failure is possibly due to #21663 |
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.
LGTM. Anyone else?
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.
💪 LGTM! Simple and safe. Thanks for your contribution @rabbitinspace ! 🚀
Yay no more changing default keychain :D thanks man |
Checklist
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validci/circleci
builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)Motivation and Context
After updating from fastlane 2.202.0 to 2.216.0
fastlane match -s $KEYCHAIN -p $PASSWORD
started to fail for me with the following error:I import wwdr certs manually after creating a keychain, so something is broken here. The weird thing I found is
security find-certificate
is invoked for the login keychain despite me specifying a separate one. After digging a bit, I figured theinstall_missing_wwdr_certificates
method doesn't take into account the-s
option.Description
This PR makes the
-s
option to be propagated to theinstall_missing_wwdr_certificates
method instead of unconditionally usingwwdr_keychain
. I found this issue which supposed to be fixed, but I guess this edge case isn't handled.Also, I hope I fixed the tests the right way.
Testing Steps