|
3.
|
|
|

If the first argument passed into get is an aspect identifier matching the 
format <account-id>/<bundle>/<aspect>, get will use the aspects configuration 
API. In this case, the command returns the data retrieved from the requested 
dot-separated aspect paths.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_get.go:54
|
|
4.
|
|
|

If the first argument passed into set is an aspect identifier matching the 
format <account-id>/<bundle>/<aspect>, set will use the aspects configuration 
API. In this case, the command sets the values as provided for the dot-separated 
aspect paths.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_set.go:49
|
|
5.
|
|
|

If the first argument passed into unset is an aspect identifier matching the 
format <account-id>/<bundle>/<aspect>, unset will use the aspects configuration 
API. In this case, the command removes the data stored in the provided 
dot-separated aspect paths.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_unset.go:42
|
|
9.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_ack.go:40
|
|
12.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_aliases.go:41
|
|
13.
|
|
|

The auto-import command searches available mounted devices looking for 
assertions that are signed by trusted authorities, and potentially 
performs system changes based on them.

If one or more device paths are provided via --mount, these are temporarily 
mounted to be inspected as well. Even in that case the command will still 
consider all available mounted devices for inspection.

Assertions to be imported must be made available in the auto-import.assert file 
in the root of the filesystem.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_auto_import.go:230
|
|
17.
|
|
|

The confinement command will print the confinement mode (strict, 
partial or none) the system operates in.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_debug_confinement.go:31
|
|
18.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_connect.go:37
|
|
19.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_connections.go:43
|
|
21.
|
|
|

The create-cohort command creates a set of cohort keys for a given set of snaps.

A cohort is a view or snapshot of a snap's "channel map" at a given point in 
time that fixes the set of revisions for the snap given other constraints 
(e.g. channel or architecture). The cohort is then identified by an opaque 
per-snap key that works across systems. Installations or refreshes of the snap 
using a given cohort key would use a fixed revision for up to 90 days, after 
which a new set of revisions would be fixed under that same cohort key and a 
new 90 days window started.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_create_cohort.go:30
|