#373 contains work to refactor the current irods role and make it work with newer irods versions.
The issue with that PR is that the irods server config template has been incrementally adapted, and we don't know which key/values in the config are necessary for irods 4 (old version) and irods 5 (new version) -- in the new irods version, some config settings have changed 'places' in the config dictionary. Details
If we can tease apart the configuration and provide a valid irods5 config file, we'll have a working component again (hopefully)! This may be an easy job for copilot?
We could either remove support for irods 4, have two separate roles, or support both in the same role conditionally.
Alternatively, we can entirely drop this plan, close #373, remove irods_server from this repo, and create new repo with a Docker-based component. I'll leave the choice up to you @chStaiger!
#373 contains work to refactor the current irods role and make it work with newer irods versions.
The issue with that PR is that the irods server config template has been incrementally adapted, and we don't know which key/values in the config are necessary for irods 4 (old version) and irods 5 (new version) -- in the new irods version, some config settings have changed 'places' in the config dictionary. Details
If we can tease apart the configuration and provide a valid irods5 config file, we'll have a working component again (hopefully)! This may be an easy job for copilot?
We could either remove support for irods 4, have two separate roles, or support both in the same role conditionally.
Alternatively, we can entirely drop this plan, close #373, remove
irods_serverfrom this repo, and create new repo with a Docker-based component. I'll leave the choice up to you @chStaiger!