On 13/05/14 17:45, Joey STANFORD wrote:
Part of the problem is that each charm is given root access on the
machine
to configure whatever services are actually needed. And there isn't
part of
the spec that has them define where the configuration files are
going, what
things they are
On Wed, May 14, 2014 at 4:06 AM, Mark Canonical Ramm-Christensen
mark.ramm-christen...@canonical.com wrote:
On Tue, May 13, 2014 at 10:45 AM, Joey STANFORD j...@canonical.com wrote:
Howdy,
On Tue, May 13, 2014 at 08:04:14AM +0400, John Meinel wrote:
I actually think this isn't about
On Wed, May 14, 2014 at 10:59:54AM +0200, Michael Nelson wrote:
ansible-playbook --check --diff
--tags=install,upgrade-charm,config-changed /path/to/playbook.yaml
[snip]
This could be made even simpler with `juju run` and a helper in the
charm... so `juju run --all check-for-diffs` would
Howdy,
On Tue, May 13, 2014 at 08:04:14AM +0400, John Meinel wrote:
I actually think this isn't about someone doing juju set-env but someone
just ssh'ing into the machine and changing things with a text editor.
Yes, this is my top concern.
Ian: Thanks for your comments and explanation. Those
On Tue, May 13, 2014 at 10:45 AM, Joey STANFORD j...@canonical.com wrote:
Howdy,
On Tue, May 13, 2014 at 08:04:14AM +0400, John Meinel wrote:
I actually think this isn't about someone doing juju set-env but someone
just ssh'ing into the machine and changing things with a text editor.
On Tue, May 13, 2014 at 4:14 AM, Joey STANFORD j...@canonical.com wrote:
Hi Juju'ers,
I'm curious to know if there is any reliable mechanism to detect a
cowboyed change inside a juju environment and then report them.
A non-juju synonym of what I'm trying to accomplish would be with puppet
I actually think this isn't about someone doing juju set-env but someone
just ssh'ing into the machine and changing things with a text editor.
Joey is the type of guy to be very concerned about people making changes
out of band that we wouldn't know about even if we had audit logging.
(Which we
