So the best practice here is to touch a file and test for the existence of
that file before running must_be_called_exactly_once()?
I think part of the issue here is that without knowing the extent of the
hook it is hard to enforce idempotency as a charm writer. It's easy to look
at the code above
, Oct 4, 2017 at 6:34 AM Stuart Bishop
wrote:
> On 4 October 2017 at 00:51, Mike Wilson wrote:
> > So the best practice here is to touch a file and test for the existence
> of
> > that file before running must_be_called_exactly_once()?
> >
> > I think part of the issu
juju hooks system. In this
> case each successive loop of the reactive runtime could better snapshot
> state and make failures more granular.
>
> * state is being renamed to flag in the next major version of reactive.
>
> On Wed, Oct 4, 2017 at 8:52 AM Mike Wilson
> wrote:
>
I tried to use the existing promulgated NFS charm and it didn't work. The
NFS server has been changed to require an export before starting and the
charm relies on using exportfs to manually create run-time exports. This
also has the unfortunate issue of not surviving reboots.
I rewrote the charm[1
