Pin plugin-backed mounts to their catalog version #171
Reference in New Issue
Block a user
Delete Branch "benvin/plugin-version-pin"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plugin-backed mounts keep their pinned
plugin_versionwhen a catalog yaml bumpsversion, so the old catalog entry is deregistered while the mount still points at it and the backend fails to start on the next leader change.mount_plugin_versionmodule tuningsys/mounts/<path>/tuneto the catalog yaml version for each plugin-backed mountcreate_before_destroy)version(removing it strands the mount on the old version)versionfrom a versioned plugin yaml removes the pin instance (no-op viadisable_delete) while CBD deregisters the versioned entry, leaving the mount pinned to a missing version (tune rejects an emptyplugin_version, so it cannot be unpinned) → add a precondition or yaml comment that a versioned plugin must stay versioned / needs a manual remountNo findings.