To simplify reasoning about their effect, the rules from the different levels/scopes are not merged but rather prioritised according to level: The rules are scoped and attached to the slot or plug side of an interface at either one of those two levels: Rules are either built-in to snapd or conveyed via assertions (signed documents) that correspond to a given snap (snap-declarations). The rule language can either express allowing or denying an auto-connection, with the latter taking precedence. The requirement for exactly one candidate can be changed.įor an interface, the candidate plug and slot pairs are determined using constraints-based rules. If there is exactly one candidate slot for a plug then an interface connection is automatically performed. It does the same for its slots and candidate plugs. Whenever a snap is installed or refreshed, snapd will review its unconnected plugs and their candidate slots for auto-connection potential. Store-set policy applies to let a given snap use an interface that would not be generally auto-connected.
There is a need to connect snaps that are designed to work together.A snap provides, or accesses, libraries or other content vital to the operation of a snap.An interface is commonly required and has no or low security implications.
#AUTO CONNECTION MANUAL#
The snapd interface auto-connection mechanism has been designed to remove the need for a manual connection when:
0 kommentar(er)
