Updated based on companion PR.

Squashed and ready for final review.

@dkocher This profile adds a general purpose profile that will work for any iRODS deployment as long as it is updated appropriately. I'm wondering if the following RENCI profile should be disabled/removed to avoid confusion?

https://github.com/iterate-ch/profiles/blob/21b3e14a075acacca96dd49188acd9b875ede7d7/iRODS%20(RENCI).cyberduckprofile

The docs reference profiles named RENCI, CyVerse Data Store, and TACC. The ones for CyVerse and TACC seem fine as they are focused on a particular deployment. The one for RENCI seems that way as well, but I don't know if the host referenced by that profile is still available.

@trel Do you know if the host referenced by the RENCI profile is still live? Do you recognize that host? I can't ping it, so maybe it's no longer active?

I would recommend we remove all the specific profiles in favor of a single default/generic one.

I would recommend we remove all the specific profiles in favor of a single default/generic one.

I am fine with dropping deprecated connection profiles. They will not be removed on client installations.

@dkocher The changes to Cyberduck bump the minimum version capability for iRODS to 4.3.2. Any user who wants to use Cyberduck to connect to an earlier version of iRODS will need a Cyberduck client of 9.3.x or earlier.

Are older versions of Cyberduck available for download?
Is documentation for older versions of Cyberduck available online for those users?

@dkocher The changes to Cyberduck bump the minimum version capability for iRODS to 4.3.2. Any user who wants to use Cyberduck to connect to an earlier version of iRODS will need a Cyberduck client of 9.3.x or earlier.

Are older versions of Cyberduck available for download? Is documentation for older versions of Cyberduck available online for those users?

I understand that previous connection profiles for deployments using deprecated iRODS version will be rendered incompatible.

• We do not maintain a versioned documentation
• Previous versions are available

Adjusted a few comments following the documentation PR. No functional changes were made to the configuration properties.

This is ready for final review.

@korydraughn Can you confirm this profile works for default installations of iRODS with no required further customization required by the user as this will be available through Preferences →Profiles.

@korydraughn Can you confirm this profile works for default installations of iRODS with no required further customization required by the user as this will be available through Preferences →Profiles.

What's the best way to do that?

I have bookmarks from earlier testing, so it's not clear if those would affect anything.

It just occurred to me that users of this profile will likely need to modify the profile unless they are working with a completely defaulted deployment, i.e. a test system.

For production systems, no one should assume this profile works as is.

It was decided that the general purpose profile in this PR will not be moving forward through this mechanism. See the conversation starting at iterate-ch/docs#632 (comment) for more context.

The profile will be provided through documentation. Users are expected to copy and paste the profile template.

Closing this PR.