"snap get" for a snap with no configuration should not be an "error"

[Robert P. J. Day]

When running "snap get" on a snap that can support configuration data but simply has none, the message printed is (for example):

# snap get snapcraft
error: snap "snapcraft" has no configuration
#

It's not clear that this rises to the level of an "error", or even a warning. Perhaps the severity of that message can be dialed back a bit.

[Sergio Cazzolato (sergio-j-cazzolato)]

Thanks for raising this.

Agree this should not be displayed/raised as an error.