You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current version of the iRODS storage plugin, default setting values other than None have priority over configured settings in the irods_environment.json file. For example: even if irods_environment.json has irods_authentication_scheme set to pam, the plugin will still use native (the default value in StorageProviderSettings).
I think it would be useful to have the plugin always use settings in the environment file, so that users don't have to copy settings from the iRODS environment file to (for example) the Snakefile. This could either be default behaviour or could be controlled by a boolean plugin setting that controls whether or not iRODS environment file settings have priority.
If this proposed change is okay, I'd be happy to submit a PR.
The text was updated successfully, but these errors were encountered:
Ensure that settings in ~/.irods/irods_environment.json have higher
priority than default setting values, so that users don't have to copy
settings from the environment file to the Snakefile.
(This is a proposed fix for issue #4)
Co-authored-by: Johannes Köster <[email protected]>
In the current version of the iRODS storage plugin, default setting values other than
None
have priority over configured settings in theirods_environment.json
file. For example: even ifirods_environment.json
hasirods_authentication_scheme
set topam
, the plugin will still usenative
(the default value inStorageProviderSettings
).I think it would be useful to have the plugin always use settings in the environment file, so that users don't have to copy settings from the iRODS environment file to (for example) the Snakefile. This could either be default behaviour or could be controlled by a boolean plugin setting that controls whether or not iRODS environment file settings have priority.
If this proposed change is okay, I'd be happy to submit a PR.
The text was updated successfully, but these errors were encountered: