loyment and
they have a very specific type of data in mind which is fetched from
stateful applications out of band by an operator.
On 19.02.2018 18:11, Liam Young wrote:
On Mon, Feb 19, 2018 at 9:05 AM, Dmitrii Shcherbakov
wrote:
Hi Liam,
I was recently looking at how to support custom conf
Hi Liam,
> I was recently looking at how to support custom configuration that
relies on post deployment setup.
I would describe the problem in general as follows:
1) charms can get context not only from Juju (config options, relation
data, leader data), environment (operating system release,
relation data by doing relation-
get without additional tools. It is also ubiquitous so we don't have to
worry about spec changes, parsing bugs and other potential problems.
Thanks for bringing this topic up.
Dmitrii Shcherbakov
___
arned
that this action is yet to be run to complete the setup or he has to
explicitly ignore it.
In my view, we should store enough configuration in leader settings so
that proper config rendering is possible during scale-out while domain
and nameserver creation can be offloaded to an operator.
T
Will be glad to help with reviews!
Thanks a lot!
Best Regards,
Dmitrii Shcherbakov
*Dmitrii Shcherbakov * | *Canonical*
Field Software Engineer
dmitrii.shcherba...@canonical.com
IRC (freenode): Dmitrii-Sh
On Wed, Mar 22, 2017 at 6:14 PM, James Page wrote:
> On Wed, 22 Mar 2017 at 15
