On 13.01.2017 17:44, Tilman Baumann wrote:
> I thought about it a little and I do think a no-op interface purely for
> peer discovery could actually help others with similar requiremrnts too.
> Hence this https://github.com/tbaumann/charm-interface-peer-discovery
>
> If there are no objections, I
On 13.01.2017 17:44, Tilman Baumann wrote:
> I thought about it a little and I do think a no-op interface purely for
> peer discovery could actually help others with similar requiremrnts too.
> Hence this https://github.com/tbaumann/charm-interface-peer-discovery
>
> If there are no objections,
I thought about it a little and I do think a no-op interface purely for
peer discovery could actually help others with similar requiremrnts too.
Hence this https://github.com/tbaumann/charm-interface-peer-discovery
If there are no objections, I will try to get this published.
This is the charm t
On 11 January 2017 at 20:23, Tilman Baumann
wrote:
> Hi,
>
> I'm writing a layered reactive-python charm which uses a peer relation
> to know all units of the same application.
>
> However I don't seem to find a way to convince charm build to create the
> ./hook/ files for this relation for me.
>
Hi Tilman
I think it's best that you create your own interface layer to do this. Then
include that interface layer in `layer.yaml` and the hooks should be
created at build time.
More info on developing interface layers:
https://jujucharms.com/docs/2.0/developer-layers-interfaces#writing-an-inter
Hi,
I'm writing a layered reactive-python charm which uses a peer relation
to know all units of the same application.
However I don't seem to find a way to convince charm build to create the
./hook/ files for this relation for me.
If I do my metadata.yaml like this and include the interface in
l
