Hi - we are in the process of creating a new snap charmed-opensearch that’s based on the current opensearch snap.
This snap will essentially be:
opensearch snap code base + multiple additional opensearch plugins
The goal of this snap is to be tailored for our opensearch charm
Therefore, I’m requesting for all the interfaces as well their autoconnections that were approved for opensearch to be approved for charmed-opensearch.
The request looks fine in general. My only question is about shmem-perf-analyzer, if I understood correctly the original request the issue was solved using private shared memory (which should auto-connect by default). Is there any reason why private shared memory is not an option anymore?
Thanks for clarifying. In that case, if I’m right the requested interfaces are:
hardware-observe:
request-type: auto-connection
log-observe:
request-type: auto-connection
mount-observe:
request-type: auto-connection
system-observe:
request-type: auto-connection
sys-fs-cgroup-service:
request-type: auto-connection
intel-qat:
request-type: auto-connection
These interface looks appropriate for charmed-opensearch and were already approved for the opensearch snap. Thus, +1 from for (#voteFor) granting auto-connection to the mentioned interfaces
process-control also needs to be approved for usage if I recall (not auto-connection), otherwise the snapstore upload will be rejected.
If that’s not the case, we’re good with the list.
Then it’s perfect, I was under the impression that an explicit approval was required for the store to approve the upload of a snap with that interface.
And for the rest of the interfaces, my understanding, is that I still need 1 approval, correct?