Skip to content

Commit

Permalink
removing obsolete caveat for ecs clusters - we've got the functionali…
Browse files Browse the repository at this point in the history
…ty now 🎉
  • Loading branch information
ina-stoyanova committed Oct 7, 2020
1 parent 158194e commit 3cbc1a6
Showing 1 changed file with 0 additions and 10 deletions.
10 changes: 0 additions & 10 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,22 +29,12 @@ The currently supported functionality includes:

_Resources: https://aws.amazon.com/about-aws/whats-new/2018/11/amazon-ecs-and-aws-fargate-now-allow-resources-tagging-/_

*DISCLAIMER:* This work is still in progress, however, you can view the advancements and changes as they happen in the open PRs of this repo.

Example usage of this functionality will be as per standard:

```shell
cloud-nuke aws --resource-type ecscluster --older-than 24h
```

<s>
- We currently do not support deleting ECS clusters because AWS
does not give us a good way to blacklist clusters off the list (there are no
tags and we do not know the creation timestamp). Given the destructive nature
of the tool, we have opted not to support deleting ECS clusters at the
moment. See https://github.com/gruntwork-io/cloud-nuke/pull/36 for a more
detailed discussion. </s>

### BEWARE!

When executed as `cloud-nuke aws`, this tool is **HIGHLY DESTRUCTIVE** and deletes all resources! This mode should never be used in a production environment!
Expand Down

0 comments on commit 3cbc1a6

Please sign in to comment.