subiquity/examples/snaps/README.md

## Sample snap data

This directory contains canned responses from snapd's REST API that
are used by default in dry-run mode. (You can pass
--no-snaps-from-examples flag to talk to your local snapd instead). It
was generated something like this:

```
$ curl --silent --unix-socket /var/run/snapd.socket a/v2/find?section=server | jq . > v2-find-section=server.json
$ for x in $(cat v2-find-section=server.json | jq -r '.result  | .[].name'); do curl --silent --unix-socket /var/run/snapd.socket a/v2/find?name=$x | jq . > v2-find-name=$x.json; done
```
add a README to examples/snaps 2018-05-22 22:14:17 +00:00			`## Sample snap data`

Make the code for talking to snapd more generic In preparation for the self-refresh and snap enterprise proxy work, both of which will require talking to the snapd API. This also makes the "snaps-from-examples" fakery happen at a lower level. 2019-03-01 00:23:03 +00:00			`This directory contains canned responses from snapd's REST API that`
			`are used by default in dry-run mode. (You can pass`
			`--no-snaps-from-examples flag to talk to your local snapd instead). It`
			`was generated something like this:`
add a README to examples/snaps 2018-05-22 22:14:17 +00:00
			```
Make the code for talking to snapd more generic In preparation for the self-refresh and snap enterprise proxy work, both of which will require talking to the snapd API. This also makes the "snaps-from-examples" fakery happen at a lower level. 2019-03-01 00:23:03 +00:00			`$ curl --silent --unix-socket /var/run/snapd.socket a/v2/find?section=server \| jq . > v2-find-section=server.json`
			`$ for x in $(cat v2-find-section=server.json \| jq -r '.result \| .[].name'); do curl --silent --unix-socket /var/run/snapd.socket a/v2/find?name=$x \| jq . > v2-find-name=$x.json; done`
add a README to examples/snaps 2018-05-22 22:14:17 +00:00			```