#general - March 2025

Hi everyone,
I'm looking for the right place to get help about Atmos.
I'm not finding every informations I need on the docs.
Where should I ask my questions ?

Hi Everyone! I just found ya'll while being super frustrated with our terraform situation at work....you guys are a godsend! Thank you thank you thank you!@!@!

Hey folks, I've been using cloudposse terraform modules to handle opsgenie setups (teams, routing rules, schedules, rotations, etc), but recently Atlassian announced that they will kill the Opsgenie product and replace it with "Jira Service Management" tool, integrated into Atlassian "Stack/UI".

And, of course, they won't keep a compatible API between opsgenie and JSM.

So, my question is.... are there any plans to implement a similar "on-call module" to JSM, as you have for Opsgenie?

Quick question for Founders&Tech Leaders.
If you were raising a round at the MVP stage again, where would you invest more - polished design or technical stability?

P.S Looking to connect with AI start-up founders.
Cheers!

That decision should depend on Marginal Profit, IMO.

Any examples of others using spa-s3-cloudfront? Getting an error when trying to plan that my app points to the terraform component app, but it does not exist in components/terraform.

I am curious if anyone has run into issues with ARC runner controller and k8s. I am able to get it working, but sporadically (pretty often) I am getting TLS handshake timeouts and just general delays in my runners. Anyone know why that would happen?

Came across this when building a custom docker image with atmos:

Error
golang-jwt/jwt: jwt-go allows excessive memory allocation during header parsing
Stacktrace
golang-jwt is a Go implementation of JSON Web Tokens. Prior to 
5.2.2 and 4.5.2, the function parse.ParseUnverified splits (via a call to strings.Split) its argument (which is untrusted data) on periods. As a result, in the face of a malicious request whose Authorization header consists of Bearer  followed by many period characters, a call to that function incurs allocations to the tune of O(n) bytes (where n stands for the length of the function's argument), with a constant factor of about 16. This issue is fixed in 5.2.2 and 4.5.2.

Does atmos have a feature similar to terragrunt where all components can be deployed for a given stack without? Is a custom workflow a requirement?

Hello SweetOps!

A few months ago, we embarked on a MASSIVE project to enable Component Testing.
The goal is to improve the stability of our components, detect and fix integration errors, and pave the way for confident delivery of new features.
In the first phase, we split the cloudposse/terraform-aws-components monorepo consisting of 160+ Terraform Components into individual repositories in the cloudposse-terraform-components GitHub organization.
Now, we are happy to announce that we have completed the second phase of this project, introducing automated tests for the first 27 components.
And we rolling on.
You can follow the status on this project board

We invite everyone to participate.

1. Help us prioritize work - Please like the “Add component tests” issue in the corresponding component repository for which you are interested in prioritizing test coverage.
2. We really need help writing tests - You can take any “Add component tests” issue with the “Good First Question” label and contribute to the test following our documentation
Read more
• https://docs.cloudposse.com/blog/automated-component-testing/
• https://github.com/orgs/cloudposse/discussions/50