Skip to content
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

Closed
cyberduck opened this issue Feb 3, 2015 · 9 comments
Closed

No longer appears to support alternate connection profiles #8539

cyberduck opened this issue Feb 3, 2015 · 9 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 3, 2015

be85312 created the issue

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:

$ ls /opt/duck/app/profiles/
DreamObjects.cyberduckprofile  Rackspace US.cyberduckprofile

Pre-upgrade connection protocols:

	URLs must be fully qualified. Paths can either denote a remote file (ftps://user@example.net/resource) or folder ftps://user@example.net/directory/) with a trailing slash.
Supported protocols
ftp	FTP (File Transfer Protocol)
	ftp://<hostname>/<folder>/<file>
ftps	FTP-SSL (Explicit AUTH TLS)
	ftps://<hostname>/<folder>/<file>
sftp	SFTP (SSH File Transfer Protocol)
	sftp://<hostname>/<folder>/<file>
dav	WebDAV (Web-based Distributed Authoring and Versioning)
	dav://<hostname>/<folder>/<file>
davs	WebDAV (HTTP/SSL)
	davs://<hostname>/<folder>/<file>
swift	Swift (OpenStack Object Storage)
	swift://<container>/<key>
s3	S3 (Amazon Simple Storage Service)
	s3://<container>/<key>
gs	Google Cloud Storage
	gs://<container>/<key>
azure	Windows Azure Storage
	azure://<container>/<key>
rackspace	Rackspace Cloud Files (US)
	rackspace://<container>/<key>
dreamhost	DreamObjects Cloud Storage (S3)
	dreamhost://<container>/<key>

Post-upgrade connection protocols:

	URLs must be fully qualified. Paths can either denote a remote file (ftps://user@example.net/resource) or folder ftps://user@example.net/directory/) with a trailing slash.
Supported protocols
ftp	FTP (File Transfer Protocol)
	ftp://<hostname>/<folder>/<file>
ftps	FTP-SSL (Explicit AUTH TLS)
	ftps://<hostname>/<folder>/<file>
sftp	SFTP (SSH File Transfer Protocol)
	sftp://<hostname>/<folder>/<file>
dav	WebDAV (Web-based Distributed Authoring and Versioning)
	dav://<hostname>/<folder>/<file>
davs	WebDAV (HTTP/SSL)
	davs://<hostname>/<folder>/<file>
swift	Swift (OpenStack Object Storage)
	swift://<container>/<key>
s3	S3 (Amazon Simple Storage Service)
	s3://<container>/<key>
gs	Google Cloud Storage
	gs://<container>/<key>
azure	Windows Azure Storage
	azure://<container>/<key>
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 3, 2015

@dkocher commented

Additional path for profiles is ~/.duck/profiles/.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 3, 2015

@dkocher commented

Broken for case sensitive file systems with changeset 3952037.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 3, 2015

@dkocher commented

In cfd48ef.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 27, 2015

be85312 commented

This appears to be a problem again as of 202a75e.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 27, 2015

@dkocher commented

Replying to [comment:6 matt wodrich]:

This appears to be a problem again as of 202a75e.
The issue is not related to this changeset.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 27, 2015

be85312 commented

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.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 27, 2015

@dkocher commented

Replying to [comment:9 matt wodrich]:

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.

I can confirm it no longer works loading profiles from ~/.duck/profiles. We have yet to find the regression.

I can confirm it no longer works loading profiles from /opt/duck/app/profiles. We have yet to find the regression.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 27, 2015

@dkocher commented

Regression in 49618bb.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 27, 2015

@dkocher commented

In 636f276.

Loading

@cyberduck cyberduck closed this Feb 27, 2015
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants