4 ms·
using names to uniquely identify infrastructure is very convenient and how most of aws already works. why not take advantage of that instead mapping name to uui
by nathants 4y ago
using names to uniquely identify infrastructure is very convenient and how most of aws already works. why not take advantage of that instead mapping name to uuid via state? in what scenario are non-stable infrastructure names useful?
- taeric 4y agoIf you are using cloud formation, it already does a uuid like name on resources it creates.
- nathants 4y agoi’m not. i do my own thing[1] with the go sdk. 1. https://github.com/nathants/libaws https://github.com/nathants/libaws
- jen20 4y agoIt certainly isn’t how “most” of AWS works. Nothing makes the name tags for important APIs like VPC or EC2 even exist, yet alone be unique. They use provider-assigned IDs instead.
- nathants 4y agovpc and ec2 are the big ones. they both support tagging atomically during create though, so it’s fine? for ec2 i’m not sure i’d want unique names per instance. typically i prefer groups of instances with the same name.