Where I work we have separate AWS accounts for production and non-production resources. I want to add a safety net where I can specify an AWS account ID in a stack and have cumulus exit if the given account ID does not match the ID associated with the AWS credentials used to make boto calls. The idea being that a non-production stack can never accidentally be run against production.
This PR adds this ability and is completely optional, all existing cumulus configs will continue working as normal.
acaire
commented
9 years ago
Where I work we have separate AWS accounts for production and non-production resources. I want to add a safety net where I can specify an AWS account ID in a stack and have cumulus exit if the given account ID does not match the ID associated with the AWS credentials used to make
botocalls. The idea being that a non-production stack can never accidentally be run against production.This PR adds this ability and is completely optional, all existing cumulus configs will continue working as normal.