Request for dm-crypt and block-devices on vaultlocker snap

store-requests privileged-interfaces
1 
- name: vaultlocker
- description: Vaultlocker provides a way to store and retrieve dm-crypt encryption keys in Vault, automatically retrieving keys and opening LUKS devices on boot.
- snapcraft: https://github.com/openstack-charmers/vaultlocker/tree/master/snap/snapcraft.yaml
- upstream: https://github.com/openstack-charmers/vaultlocker
- upstream-relation: The OpenStack team maintains the application and snap
- interfaces:
	- dm-crypt:
		- request-type: auto-connection
		- reasoning: Required for vault locker to set up, lock, and unlock LUKS devices. Vaultlocker retrieves the encryption key from Vault and uses it to open the encrypted device, including automatically during boot.
	- block-devices:
		- request-type: auto-connection
		- reasoning: Required for vaultlocker to access and operate on the underlying block devices containing LUKS volumes. Vaultlocker needs access to these devices to encrypt them and subsequently unlock them using keys retrieved from Vault.
2

This request has been added to the queue for review by the @reviewers team.

3

Hello @wolsen,

Reasonable and expected access to provide the vaultlocker snap’s basic functionality. This is a +1 from me for granting auto-connection of both the dm-crypt and block-devices interfaces for the vaultlocker snap.

4

+1 from me as well to grant auto-connection of dm-crypt and block-devices interfaces to vaultlocker snap.

5

Hi @wolsen,

Apologies for the delay on this request, +2 votes for, 0 votes against, granting auto-connect of interfaces dm-crypt and block-devices to snap vaultlocker. This is now live.