only update the keystore if the private key matches the certificate#9
Open
jcvrabo wants to merge 2 commits intocloudfoundry:mainfrom
Open
only update the keystore if the private key matches the certificate#9jcvrabo wants to merge 2 commits intocloudfoundry:mainfrom
jcvrabo wants to merge 2 commits intocloudfoundry:mainfrom
Conversation
Author
|
I have signed the easyCLA, but the bot complains about mindprogenitor, which I don't even know why it's following and added to this pull request as that is another personal account I have while jcvrabo is the account I'm making the pull request with (and owner of the fork) which is the user for my organization |
|
Just realized that the commit was done with this account... also signed the easyCLA with it. All done. Hope this can be reviewed and merged soon. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As a solution for the opened issue #8