The new --retain-traffic-data flag works the same way as the old default behavior of cluster-destroy; I just added a check that they provided either that flag or --destroy-everything to make the choice explicit and obvious.
Tested the new option locally against my AWS account:
(.venv) chelma@3c22fba4e266 aws-aio % ./manage_arkime.py --region us-east-1 cluster-destroy --name MyCluster
2024-01-19 15:02:13 - Debug-level logs save to file: /Users/chelma/workspace/Arkime/aws-aio/manage_arkime/manage_arkime.log
2024-01-19 15:02:13 - Using AWS Credential Profile: None
2024-01-19 15:02:13 - Using AWS Region: us-east-1
2024-01-19 15:02:13 - You must specify either --destroy-everything or --retain-traffic-data
2024-01-19 15:02:13 - Aborting...
License
I confirm that this contribution is made under an Apache 2.0 license and that I have the authority necessary to make this contribution on behalf of its copyright owner.
Description
--retain-traffic-dataflag works the same way as the old default behavior ofcluster-destroy; I just added a check that they provided either that flag or--destroy-everythingto make the choice explicit and obvious.Tasks
Testing
License
I confirm that this contribution is made under an Apache 2.0 license and that I have the authority necessary to make this contribution on behalf of its copyright owner.