You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As documented in the README, aws-nuke refuses to run as soon as it detects the presence of the (substring) prod in the AWS account alias.
However, it is also not uncommon to use a string such as nonprod (!) in the alias for accounts that not in production use, and these are precisely the kinds of accounts one may want to use aws-nuke against, as they are used for experimentation.
Rather than be forced to fork the repo (to make a trivial change to remove the hard-coding), we are requesting that the user be allowed to specify a choice for this kind of safeguard.
This is currently an impediment to our intended use of aws-nuke
The text was updated successfully, but these errors were encountered:
We have the same issue that OP described. It's not possible to nuke nonprod accounts. Also all accounts that have productivity or producer in the name won't be nuked.
As documented in the README,
aws-nuke
refuses to run as soon as it detects the presence of the (substring)prod
in the AWS account alias.However, it is also not uncommon to use a string such as
nonprod
(!) in the alias for accounts that not in production use, and these are precisely the kinds of accounts one may want to useaws-nuke
against, as they are used for experimentation.Rather than be forced to fork the repo (to make a trivial change to remove the hard-coding), we are requesting that the user be allowed to specify a choice for this kind of safeguard.
This is currently an impediment to our intended use of
aws-nuke
The text was updated successfully, but these errors were encountered: