Auto-connect request for datashare

[pirhoo]

Hello @alexmurray, thanks for the review!

I tried first without these interfaces but it looks like ElasticSearch needed them to start correctly:

Limitation when writing to SNAP_USER_COMMON

I built the snap locally and the lock for node 0 is created in $SNAP_USER_COMMON. It’s also trying to create network sockets and perform other system-related operations, so you can try to add network, network-bind, system-observe, and mount-observe to the plugs list. Note that mount-observe and system-observe don’t auto-connect, you need to connect them manually with snap connect datashare:mount-observe and snap connect datashare:system-observe (or request auto-connect permissions for those inte…

I reviewed them again:

• system-observe I thought this was needed but after disconnecting it, I can see ElasticSearch starts normally. Sorry, I should have checked earlier!
• mount-observe is required by ElasticSearch to inspect the quota information. When initializing, ElasticSearch needs to gather information about the system and ensure the cluster is healthy. For instance, it checks the available disk space. Not connecting this interface triggers a java.io.IOException: Mount point not found error.

I corrected the snapcraft.yml following your advice. The latest revision is here:

https://dashboard.snapcraft.io/snaps/datashare/revisions/8/

Thanks again!