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
No longer appears to support alternate connection profiles #8539
Comments
Additional path for profiles is |
This appears to be a problem again as of 202a75e. |
Sorry, I should have said I upgraded to 4.7.17009 and found that it was the case again, not that it was specifically that changeset. I'm not sure what intermediate changeset might have caused it, just that that's the version I'm running at the moment. |
Replying to [comment:9 matt wodrich]:
I can confirm it no longer works loading profiles from |
Before upgrade to 4.7.16658, I saw the rackspace connection profile in duck --help as a protocol, and the dreamhost connection profile I had added in the same directory as well; after the upgrade, neither is present. I hoped there had just been a change in help text generation, so I tried the protocol, and it was unrecognized. Is there a mechanism for re-registering connection profiles, or has the support been removed or broken between versions? I have verified that both files are still there. I was previously running version 4.6.2.16478.
command to verify connection profile presence:
Pre-upgrade connection protocols:
Post-upgrade connection protocols:
The text was updated successfully, but these errors were encountered: