https://cloudposse.com logo
Join Slack
Powered by
Congrats on the `atmos` v1 golang rewrite release!...
# geodesic
b
Congrats on the 
atmos
v1 golang rewrite release! 🎉 Huge improvement over the 
variant
based version. Those new 
ATMOS_
envs configs are great additions. @Erik Osterman (Cloud Posse) @Andriy Knysh (Cloud Posse) https://github.com/cloudposse/atmos/releases/tag/1.0.0
🙌 4
🎉 4
🙏 1
This is means the stack yaml parser are the same for 
atmos
and 
cloudposse/utils
TF provider. Right?
a
It’s the same
The new atmos has a few improvements
So we need to use the code from atmos in the provider and not repeat it in two places
Update to the provider is coming
b
That is great! Love the work.
I need to figure out why the TF workspace names are different the two version. The new v1, is naming the workspace as 
{environment}-{stage}-{base-component-name}
but the older atmos would name it 
{environment}-{stage}-{component-name}
. The prefix works the same with both. Only the workspace name is affected. Once I can figure it out, I am moving everything to v1.
a
oh, the new one uses ``{environment}-{stage}-{base-component-name}` as the prefix?
this is an oversight, will fix for backwards compatibility (although the name does not matter for new deployments)
b
Yes. I tried to re-deploy something I had previously deployed. I noticed it was trying to create all the resources because it was using different workspace (s3) name.
a
A new release is coming today
🙏 1
👍 1
e
other nice enhancements are: • nested component folders • nested stack configs • new top level commands like 
atmos describe component
• fixed backend.tf generation
🙌 1
@Andriy Knysh (Cloud Posse) I do think we should update the main 
README
with all the new commands and features
a
yes we should (will do it in the course of a few days)
(fixed what you found with TF workspace for the derived components, not it works as the old atmos)
b
Thank you. I'll be checking it out later today.
Works perfectly sir. 👏
✅ 1
e
Also, we fixed our packages repository (deb, rpm, apk) and it now has the latest versions
🙌 1
m
are the modules 
terraform-aws-components
going to be updated for 1.0?
e
someday 😉
😁 1
first we want to solve vendoring with atmos. once we do that I think we're closer to supporting it.
we want to make it easier to upstream and downstream components via git
m
makes sense
what's the issue with vendoring now?
e
internally, there's a huge desire to support vendering. it comes up every single week. it's been held up on the atmos rewrite, which is now done. So I hope it unlocks that functionality sooner rather than later.
we want to support vendoring natively in atmos as a core functionality.
so stack configs can specify an upstream origin and version
then run an atmos command to pull from there (and eventually push via a PR)
basically, when you run 
terraform init
that is vendoring the providers locally
we want something like that in atmos for components
m
slick
e
then imagine things like 
atmos terraform upgrade eks
(not sure the interface yet... maybe 
atmos upgrade component eks
m
yeah, is there a way to test any of the interdependencies?
e
no, i don't see that ever being in scope
(too complex to merit the investment)
m
yeah
e
I do see us adding terratests to components
also, i see us adding support to import any module and make it a component dynamically
e.g. 
atmos terraform generate component vpn <https://github.com/cloudposse/terraform-aws-ec2-client-vpn> --version 0.2.0
(terraform components are opinionated terraform root modules that wrap other modules and have a state backend defined, which child modules do not have)
m
would that set up the providers as well
e
that's already handled by terraform, so we don't need to do anything about that
(we wouldn't advise committing providers to source control)
our objective here is to support gitops best practices, vendoring and committing the source into the repo
m
for providers, i was referencing the way the modules are set up in 
terrafrom-aws-components
e
I'm not following
m
b
You guys are on point. Love the addition with v1.2; especially 
ATMOS_LOGS_VERBOSE
. I have been using it daily since v1.1. I think the only thing missing is 
atmos workflow
. Once it is available, assuming it will be, I can push it out to all our CI and teams.
a
Workflows are coming soon, thanks again for testing
Open in Slack
PreviousNext
Powered by