-
Notifications
You must be signed in to change notification settings - Fork 290
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
Fixes #28349 - refactors importer comparison #8455
Conversation
Issues: #28349 |
🔥 🔥 🔥 🔥 🔥 |
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
ece0687
to
be2a718
Compare
if generated_config['proxy_password'] == "" && capsule_config['proxy_password'] == "*****" | ||
generated_config.delete('proxy_password') | ||
capsule_config.delete('proxy_password') | ||
end |
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.
to clarify, if generated_config['proxy_password']
is set, it will always refresh the importer. Is that what we want?
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.
Is your suggestion to always ignore proxy_password
in the comparison? Since pulp2 will always return that masked string (if set previously to any value), it seems like any comparison will fail.
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.
possibly, but i was more opening up debate :)
I think this is the safter thing to do is the way you have it, although it makes #8415 not really work if you're using an http proxy, although thats not really a problem introduced by this pr. So i guess yes lets leave it the way you have it 👍 but we should probably open a bug around this to discuss how to properly address it (especially with pulp3)
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.
Hopefully this isn't an issue in pulp3.
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.
We could ask pulp2 to be fixed to resolve this. That's another option.
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.
I checked and pulp3 returns the full proxy url:
{"pulp_href":"/pulp/api/v3/remotes/file/file/c6688395-58f8-461a-bd3e-145083741543/","pulp_created":"2019-11-26T19:11:49.606085Z","name":"proxytest-137322","url":"http://foo.com/bar/PULP_MANIFEST","ca_cert":null,"client_cert":null,"client_key":null,"tls_validation":true,"proxy_url":"http://boobar:boobar@foo.com","pulp_last_updated":"2019-11-26T19:12:43.872594Z","download_concurrency":20,"policy":"immediate"}
however i suspect that might be a bug ;)
I think this is fine for now!
I gave this a test by calling |
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.
ACK based on @ianballou 's testing
don't forget to squash! |
This PR addresses a pulp2 bug where the proxy password is returned as a masked string.
This condition triggers repo refreshes unnecessarily.