Re: CLI UX for plugs with parameters?

2016-09-22 Thread Simon Fels
You wont set the attribute of the slot/plug in the command line you use to
connect slot and plug. Every attribute as to be set in the definition of
the plug/slot. Like

plugs:
  my-plug:
interface: really-awesome-interface
attribute1: value1
...

Then you simply connect via

$ snap connect my-snap:my-plug ..

without specifying  any attributes.

regards,
Simon


On Tue, Sep 20, 2016 at 9:52 AM, Stuart Bishop 
wrote:

> Hi.
>
> I believe that slots will have support for arguments, for example allowing
> a snap to connect to the 'home' slot and provide an argument requesting
> access to hidden files.
>
> Does anyone know what the command line interface will look like?
>
> In the snap layer for Juju, I need to define the data structure to declare
> what additional connections need to be made after installation of the snap.
> I'd like to get this right the first time since I'm going to be stuck with
> it.
>
>
> --
> Stuart Bishop 
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


CLI UX for plugs with parameters?

2016-09-20 Thread Stuart Bishop
Hi.

I believe that slots will have support for arguments, for example allowing
a snap to connect to the 'home' slot and provide an argument requesting
access to hidden files.

Does anyone know what the command line interface will look like?

In the snap layer for Juju, I need to define the data structure to declare
what additional connections need to be made after installation of the snap.
I'd like to get this right the first time since I'm going to be stuck with
it.


-- 
Stuart Bishop 
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft