search

irods / irods_rule_engine_plugin_metadata_guard

BSD 3-Clause "New" or "Revised" License
0 stars 7 forks source link

A question about a possibility of an enhancement of the guard scope #44

Open mstfdkmn opened 2 years ago

mstfdkmn commented 2 years ago

Currently the plugin is being enabled by configuring it for the zone collection - /tempZone. In other saying we add some sort of configuration metadata to the zone collection. And this is making the plugin effective on the entire zone.

However for the possibilities like some certain metadata should only be guarded once attached to a specific group/project, the following configuration as expected not working. imeta set -C /tempZone/home/groupA irods::metadata_guard '{"prefixes": ["irods::"], "admin_only": true}'

An alternative solution for this might be adding an extra layer for the namespace. imeta set -C /tempZone irods::metadata_guard '{"prefixes": ["group1::irods::"], "admin_only": true}'

However we are worried to make things complex in future: we believe the namespacing should be used only for identifying something.

What would be your opinion for a use case that needs to protect a specific metadata only for a specific collection/group? Thanks.

trel commented 2 years ago

This should definitely work as expected:

imeta set -C /tempZone/home/groupA irods::metadata_guard '{"prefixes": ["irods::"], "admin_only": true}'

If it is not working, please share a bug report.

I looked at the tests... but don't see one that isn't at the root of the zone, so regardless, we should add one.

trel commented 2 years ago

new issue created here: https://github.com/irods/irods_rule_engine_plugin_metadata_guard/issues/45