I really like aws-tagger and have enjoyed using it.
I'm working to apply cost allocation tags for my teams's AWS infrastructure. We use a wide variety of AWS resources, so if I use aws-tagger, I'm planning to add support for 10-20 more AWS resource types.
I need to build out the ability to scan AWS resources that don't have a specific tag (eg, scan for non-free AWS resources where my-cost-allocation-tag does not exist or is null). My end goal is to be able to tag AWS infrastructure and confirm I've cost allocated 100% of my teams's AWS spend. I believe this would be new functionality for aws-tagger. Would this be a welcome addition to the package?
If so, happy to collaborate and make the modifications here. If not, I'm planning to fork the code and create a new package (and name it something besides aws-tagger). Or maybe there are other alternatives besides these 2 outcomes.
Either way, thanks for open sourcing the tool!
CC/ @patrickbcullen
I really like
aws-taggerand have enjoyed using it.I'm working to apply cost allocation tags for my teams's AWS infrastructure. We use a wide variety of AWS resources, so if I use
aws-tagger, I'm planning to add support for 10-20 more AWS resource types.I need to build out the ability to scan AWS resources that don't have a specific tag (eg, scan for non-free AWS resources where
my-cost-allocation-tagdoes not exist or is null). My end goal is to be able to tag AWS infrastructure and confirm I've cost allocated 100% of my teams's AWS spend. I believe this would be new functionality foraws-tagger. Would this be a welcome addition to the package?If so, happy to collaborate and make the modifications here. If not, I'm planning to fork the code and create a new package (and name it something besides
aws-tagger). Or maybe there are other alternatives besides these 2 outcomes.Either way, thanks for open sourcing the tool!
CC/ @patrickbcullen