moved action validation into context package; context tests not yet fixed
tests WIP
Modified PowerShell Charm resources dir.
merge parent, resolve conflicts
merge imminent future parent, fix conflicts
Meter status support in metrics collector wire format.
Ignore conflict error when releasing maas nodes
Remove obsolete comment
beef up tests
Merge branch 'uniter-context-export-flush' into uniter-action-context-2
finally fix crazy tests in not-very-happy-making way
Move types out to a third part to break the dependency cycle
state: more type shuffling
state: move moving things around
Merge branch 'master' into uniter-action-context-2
gb ./... passes
drop redundant runner code
address review
Comment update
Merge pull request #1095 from voidspace/maas-1381619

Ignore conflict error when releasing maas nodes

When releasing a node that is not in a releasable status, i.e. typically is already released, maas returns an error 409. Instead of dying and refusing to destroy environment we now ignore that error.

Error 409 is only used for a limited set of statuses, so this seems like safe behaviour. See: https://bugs.launchpad.net/maas/+bug/1381619/comments/15

Fixes bug 1381619.