-
Notifications
You must be signed in to change notification settings - Fork 897
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
Use credential callback to set credentials #14889
Conversation
@gmcculloug @Fryguy @eclarizio |
@gmcculloug bump |
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.
Any way we can add specs for the methods that were changed in lib/git_worktree.rb
? The larger amount of changes in that file worry me more without specs.
This pull request has been automatically closed because it has not been updated for at least 6 months. Feel free to reopen this pull request if these changes are still valid. Thank you for all your contributions! |
This pull request is not mergeable. Please rebase and repush. |
953fd0f
to
115f021
Compare
Checked commits mkanoor/manageiq@115f021~...4928e89 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@gmcculloug Please review |
Use credential callback to set credentials (cherry picked from commit 2dd64f8) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1568602 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1568604
Gaprindashvili backport details:
|
Use credential callback to set credentials (cherry picked from commit 2dd64f8) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1568603 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1568605
Fine backport details:
|
Use credential callback to set credentials (cherry picked from commit 2dd64f8) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1568603 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1568605
https://bugzilla.redhat.com/show_bug.cgi?id=1443106
https://bugzilla.redhat.com/show_bug.cgi?id=1552274
Rugged works using callbacks for credentials. The callback can be either a credential object or a callback that returns a credential object. If the credentials are invalid the callback is called again, it is designed to be used in a UI, where the UI can prompt the user for entering the updated userid/password. If the user doesn't want to enter the userid/password they can cancel it.
Since the callback is being called repeatedly it gives the feeling that the UI is stuck or the rake import command is stuck.
We record that the credential has been set once in the callback and if called again it raises an exception which rugged sends back to the caller.
Links