[09:54] bthomas: The pgsql interface is no longer in my playpen and 1.0.0 can be found at https://github.com/canonical/ops-lib-pgsql . [09:56] thanks stub : the problem I was facing was I had not setup my global git config to work with launchpad. Chipaca noticed that and helped me fix the issue. Will have a look at ops-lib-pgsql. [09:56] The updated version means you don't need that ;) [09:57] Functionally it is the same [09:57] (so far) [10:39] Issue operator#395 opened: juju-info not supported [11:12] ¡Muy buenos días a todos! [12:25] jam, I have a juju question, to see if something is possible... let's say I have two units, one with Apache and other with my charm, the human operator relates both, so I get a 'relation-changed' event [12:25] when handling that event, I do `event.relation.data[self.unit]['ports'] = '80'`, so I'm configuring Apache to work on the port 80, for example [12:26] but let's say that in the future my charm's config changes, and I want to tell Apache to listen in a different port... can I do that? how? because at that moment I don't have "the event from the Apache unit" to write into... [13:33] facubatista: but you have 'config-changed' as the event [13:33] and you can do [13:33] self.model.get_relation('apache').data[self.unit]['ports'] = '80' [13:33] or better: [13:33] for relation in self.model.relations['apache']: [13:34] relation.data[self.unit]['ports'] = '80' [13:34] And that will trigger relation-changed on Apache [13:34] the loop and/or relation = self.model.get_relation(); if relation is not None: [13:34] would let you do the check to see if you actually are related to apache when you get config-changed [13:52] jam, ah, getting the relations through `self.model.relation` is what we were not finding how to do with davigar15_ , thanks!!! [13:52] np === Dmitrii-Sh1 is now known as Dmitrii-Sh