Michael Barrett

Yes - though I've left it sort of loose so that people can do it anyway that they want. In the end it comes down to this: In your nodes.yaml...

BTW, there may be room for a more generic way of doing this and I might write a daemon to do so at some point - but there are many...

This is mostly handled by suppressions, but it's not quite the same, so leaving this open.

Provided a not_soft_recovery filter - leaving this open to think about it some more, but at least now it's possible to ignore soft recovery emails.

Hmm - need some more thought on this. In the case that a handler fails should the result not get deleted? In the case that there are multiple handlers, if...

Hey @mromaszewicz - I did a quick run through this to update it to use some of the concepts we've been pulling into newer blueprints (things like properties for variables,...

So the allure of naming things is really dangerous - it's bitten me in the past a ton of times, so much so that I really think the benefits are...

BTW, an example of not using naming - at my new company, we setup ECS clusters with this. With these settings: ``` namespace: modsy-dev stack_name: wrc-cluster resource: Cluster ``` And...

This is partially handled by the new REST API

An issue is that the config.yaml is loaded separately from the resources.yaml, which results in two different version hashes. Not sure what to do with that - combine them? Create...