Question for you folks. Now that we can create components from upstream modules and even claude our own components, are ALL the cloudposse components still relevant and worth maintaining and creating new components? To push even further back, are there any modules that are so simple that aren't worth migrating to or using? If any are flagged, will those repos be archived or will their readmes eventually be updated to use the newer/modern approach?

To be clear, components are not to be confused with atmos; atmos exists as a product outside of our modules. I want to make this clear, because many people new to atmos think they have to use our components, our terraform, our modules. When instead, these are examples of how we use them.

I know you can claude your components away and use the very best for_each , and the supersuper new functions and all that but the interconnection between components is not that easy to get with one prompt. And at the end of the day AI needs and example to base itself from, therefore you need CP modules as an example. There is going to come a day where Atmos or another tool will just simple interact with the AWS MCP already allowed in your account with certain identity centre role/oidc and you will be able to just instantiate the resource in the stack and it will just interact directly with the API without needed TF anymore. That day is coming, I'm just planning to be retired by then.

Speaking on this. We have a bunch of components that rely on eachother, say for a specific application. We use workflows to deploy them, in order. Is that in line with how the tool should be used? ( we dont have space lift or any "nice QOL" tooling)

😃