Can no longer install snaps with multiline plugs

[Chad Smith]

Potential regression:
A snap we have been writing published in the beta channel has been successfully installing for a few weeks. I just updated my snap-related packages to the following and now that snap install fails parsing the snap header.

ii snap-confine 1.0.38-0ubuntu0.16.04.8 amd64 Support executable to apply confinement for snappy apps
ii snapcraft 2.17 all easily craft snaps
ii snapd 2.14.2~16.04
ii ubuntu-core-launcher 1.0.43-0ubuntu1~16.04.1

- Fetch and check assertions for snap (6) (parsing assertion headers: expected 4 chars nesting prefix after multiline introduction "plugs:": " hardware-observe:")

Our snapcraft.yaml has the following defined for plugs definitions

plugs: [ network-bind, network-control, kernel-module-control, system-observe, hardware-observe ]

[Gustavo Niemeyer (niemeyer)]

This is actually a problem in the snap-declaration assertion, not in the snap itself.

We need to review the assertion text and see if that's a bug in the parser or in the text itself. More likely it's the latter.

[Jamie Strandboge (jdstrand)]

These changes in the store have been reverted so your snap should start working again. Let us know if it does not.

[Chad Smith (chad.smith)]

targeting this to snapcraft as the snap can be installed locally via --force-dangerous without header parse errors. This seems to be the yaml parsing the snapcrafts auto-plugging feature.

[Chad Smith (chad.smith)]

@Gustavo and @Jaime the fix to the snap-declaration assertion revert must have solved this. I can now install those snaps without seeing this issue. Thanks for the fast response!

[Sergio Schvezov (sergiusens)]

Moving back to snappy