Browsing Czech translation

28.

The fde-setup-request command is used inside the fde-setup hook. It will
return information about what operation for full-disk encryption is
requested and auxiliary data to complete this operation.

The fde-setup hook should do what is requested and then call
"snapctl fde-setup-result" and pass the result data to stdin.

Here is an example for how the fde-setup hook is called initially:
$ snapctl fde-setup-request
{"op":"features"}
$ echo '[]' | snapctl fde-setup-result

Alternatively the hook could reply with:
$ echo '{"error":"hardware-unsupported"}' | snapctl fde-setup-result

And then it is called again with a request to do the initial key setup:
$ snapctl fde-setup-request
{"op":"initial-setup", "key": "key-to-seal", "key-name":"key-for-ubuntu-data"}
$ echo "$sealed_key" | snapctl fde-setup-result

29.

The fde-setup-result command sets the result data for a fde-setup hook
reading it from stdin.

For example:
When the fde-setup hook is called with "op":"features:
$ echo "[]" | snapctl fde-setup-result

When the fde-setup hook is called with "op":"initial-setup":
$ echo "sealed-key" | snapctl fde-setup-result

30.

The file-access command returns information about a snap's file system access.

This command is used by the xdg-document-portal service to identify
files that do not need to be proxied to provide access within
confinement.

File paths are interpreted as host file system paths. The tool may
return false negatives (e.g. report that a file path is unreadable,
despite being readable under a different path). It also does not
check if file system permissions would render a file unreadable.

31.

The find command queries the store for available packages.

With the --private flag, which requires the user to be logged-in to the store
(see 'snap help login'), it instead searches for private snaps that the user
has developer access to, either directly or through the store's collaboration
feature.

A green check mark (given color and unicode support) after a publisher name
indicates that the publisher has been verified.

32.

The forget command deletes a snapshot. This operation can not be
undone.

A snapshot contains archives for the user, system and configuration
data of each snap included in the snapshot.

By default, this command forgets all the data in a snapshot.
Alternatively, you can specify the data of which snaps to forget.

33.

The get command prints configuration options for the current snap.

$ snapctl get username
frank

If multiple option names are provided, a document is returned:

$ snapctl get username password
{
"username": "frank",
"password": "..."
}

Nested values may be retrieved via a dotted path:

$ snapctl get author.name
frank

Values of interface connection settings may be printed with:

$ snapctl get :myplug usb-vendor
$ snapctl get :myslot path

This will return the named setting from the local interface endpoint, whether a plug
or a slot. Returning the setting from the connected snap's endpoint is also possible
by explicitly requesting that via the --plug and --slot command line options:

$ snapctl get :myplug --slot usb-vendor

This requests the "usb-vendor" setting from the slot that is connected to "myplug".

34.

The get command prints configuration options for the provided snap.

$ snap get snap-name username
frank

If multiple option names are provided, the corresponding values are returned:

$ snap get snap-name username password
Key Value
username frank
password ...

Nested values may be retrieved via a dotted path:

$ snap get snap-name author.name
frank

35.

The help command displays information about snap commands.

36.

The info command shows detailed information about snaps.

The snaps can be specified by name or by path; names are looked for both in the
store and in the installed snaps; paths can refer to a .snap file, or to a
directory that contains an unpacked snap suitable for 'snap try' (an example
of this would be the 'prime' directory snapcraft produces).

37.

The install command installs the named snaps on the system.

To install multiple instances of the same snap, append an underscore and a
unique identifier (for each instance) to a snap's name.

With no further options, the snaps are installed tracking the stable channel,
with strict security confinement.

Revision choice via the --revision override requires the user to
have developer access to the snap, either directly or through the
store's collaboration feature, and to be logged in (see 'snap help login').

Note that a later refresh will typically undo a revision override, taking the snap
back to the current revision of the channel it's tracking.

Use --name to set the instance name when installing from snap file.