SweetOps · Cloud Posse’s open source community

Connect with the people behind Cloud Posse’s open source

Meet the maintainers and engineers using Atmos and Terraform. Ask questions, compare notes, and share what you’re building.

Join the conversation

A community built around open source

SweetOps brings together Cloud Posse maintainers and the engineers using our open source. Ask questions about Atmos and Terraform, discuss design decisions, and share what you’re learning.

Talk with maintainers

Ask about Atmos, Terraform modules, and the thinking behind our tools. Bring your questions and context.

Compare notes with users

Learn how other engineers use Cloud Posse’s open source in their environments. Share what worked—and what didn’t.

Help shape the tools

Discuss releases, suggest improvements, and find opportunities to contribute to the projects you use.

Browse Archive

Search years of DevOps discussions, Terraform tips, and community knowledge.

Community Testimonials

What Our Members Say

What people have found useful about being part of SweetOps.

Ryan Smith

Calm

Kudos again to this slack team. Cloud Posse being an open source DevOps hub is really a great thing. I often talk to other DevOps peeps and mention Cloud Posse and this culture.

Val Naipaul

The Adaptavist Group

I would recommend Cloud Posse both for their expertise as an AWS integrator, and their culture of openness and excellence. The community is well-moderated, welcoming, leading-edge, and attracts thoughtful contributions.

Kris Musard

Obsidian Tek

Cloud Posse engages with the open source community through their Slack channel and weekly online office hours. Cloud Posse genuinely cares about helping other technologists find the best solutions, regardless of whether they are paying customers or not.

See What People Are Discussing

Browse real conversations from our community

Daniel Booth7 days ago

Ah just looked into it diff and plan operations are allowed on abstract components

2 replies

Daniel Booth7 days ago

is that intentional?

Daniel Booth7 days ago

I understand the recommendation is to use the official helm component type now but we use helmfile elsewhere so still preference it

Daniel Booth7 days ago

I think I may have found another bug, I have an abstract helmfile component in my catalog and when I run atmos helmfile diff it says it will create the release in the cluster:

metadata:
  component: reflector
  inherits:
    - reflector/defaults
  type: abstract

…/catalog/k8s-apps ❯ atmos helmfile diff -s ops-cluster-apps reflector
Adding repo emberstack <https://emberstack.github.io/helm-charts>
"emberstack" has been added to your repositories
Comparing release=reflector, chart=emberstack/reflector, namespace=reflector
reflector, reflector, ClusterRole (<http://rbac.authorization.k8s.io|rbac.authorization.k8s.io>) has been added:
-
+ # Source: reflector/templates/clusterRole.yaml
+ apiVersion: <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>
+ kind: ClusterRole
+ metadata:
+   name: reflector
+   namespace: reflector
+   labels:

Daniel Booth8 days ago

I have quite a few use cases for this.

5 replies

Daniel Booth8 days ago

is this currently possible?

Daniel Booth8 days ago

It would be cool if there was a way to adjust secret references based on profiles or something

1 reply

Alex Renoki9 days ago

Seems like the latest release of Atmos is failing the signature check when using .tool-versions:

 ❯ atmos toolchain install
[...previous tools...]
✗ Install failed : failed to verify downloaded asset: signature verification failed: .tools/bin/sigstore/cosign/v3.1.4/cosign [verify-blob --certificate-identity-
  regexp ^<https://github.com/cloudposse/.github/.github/workflows/shared-go-auto-release.yml@> --certificate-oidc-issuer <https://token.actions.githubusercontent>.
  com --
  bundle /var/folders/s3/x60v087551sg6kdzjm3r4sjr0000gn/T/atmos-verify-559584549.json /var/folders/s3/x60v087551sg6kdzjm3r4sjr0000gn/T/atmos-checksum-
  652188209.2_SHA256SUMS]: exit status 1
  Error: failed to verify certificate identity: no matching CertificateIdentity found, last error: expected SAN value to match regex
  "^<https://github.com/cloudposse/.github/.github/workflows/shared-go-auto-release.yml@>", got "<https://github.com/cloudposse/atmos/.github/workflows/release->
  pipeline.yml@refs/heads/main"
  error during command execution: failed to verify certificate identity: no matching CertificateIdentity found, last error: expected SAN value to match regex
  "^<https://github.com/cloudposse/.github/.github/workflows/shared-go-auto-release.yml@>", got "<https://github.com/cloudposse/atmos/.github/workflows/release->
  pipeline.yml@refs/heads/main"
✗ Install failed : failed to verify downloaded asset: signature verification failed: .tools/bin/sigstore/cosign/v3.1.4/cosign [verify-blob --certificate-identity-
  regexp ^<https://github.com/cloudposse/.github/.github/workflows/shared-go-auto-release.yml@> --certificate-oidc-issuer <https://token.actions.githubusercontent>.
  com --
  bundle /var/folders/s3/x60v087551sg6kdzjm3r4sjr0000gn/T/atmos-verify-559584549.json /var/folders/s3/x60v087551sg6kdzjm3r4sjr0000gn/T/atmos-checksum-
  652188209.2_SHA256SUMS]: exit status 1
  Error: failed to verify certificate identity: no matching CertificateIdentity found, last error: expected SAN value to match regex
  "^<https://github.com/cloudposse/.github/.github/workflows/shared-go-auto-release.yml@>", got "<https://github.com/cloudposse/atmos/.github/workflows/release->
  pipeline.yml@refs/heads/main"
  error during command execution: failed to verify certificate identity: no matching CertificateIdentity found, last error: expected SAN value to match regex
  "^<https://github.com/cloudposse/.github/.github/workflows/shared-go-auto-release.yml@>", got "<https://github.com/cloudposse/atmos/.github/workflows/release->
  pipeline.yml@refs/heads/main"

[...rest of the tools...]

✗ Installed 0 tools, failed 1, skipped 13

In my .tool-versions I have this:

atmos 1.233.2

16 replies

Daniel Booth10 days ago

Hey, having an issue with metadata.component inheritance in Atmos 1.233.0.

My stack inherits an abstract with metadata.component: lxd/talos-nodes. describe component shows that inherited metadata, but the top-level component
remains k8s_nodes. During describe affected, an atmos component lookup then tries using the nonexistent components/terraform/k8s_nodes directory.

catalog entry:

  k8s_nodes/lxd/defaults:
    metadata:
      type: abstract
      component: lxd/talos-nodes

stack entry:

  k8s_nodes:
    metadata:
      inherits:
        - k8s_nodes/lxd/defaults

Setting metadata.component explicitly on the stack entry fixes it...

is this intended behaviour?

4 replies

erik12 days ago

Heads up github.com/cloudposse/atmos/issues/3475

13 replies

View Full Archive

Come join the conversation.

Meet the maintainers and practitioners behind the tools you use. Ask a question, share an experience, or just listen in.

SweetOps is a free community, not a guaranteed support channel. Replies depend on people’s availability. Need dedicated help? Talk to us about paid support.