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

Proposed change: allow irods_environment.json to override default settings #4

Open
stsnel opened this issue Feb 5, 2024 · 2 comments

Comments

@stsnel
Copy link
Collaborator

stsnel commented Feb 5, 2024

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.

@johanneskoester
Copy link
Contributor

Yes, I completely agree. Looking forward to your PR! Also, would you be interested to become an official maintainer of this plugin?

@stsnel
Copy link
Collaborator Author

stsnel commented Mar 8, 2024

Thanks, I'd be happy to help out with maintaining the plugin where I can.

I expect to be able to send a PR for this change shortly.

johanneskoester added a commit that referenced this issue Aug 14, 2024
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants