#refarch (2024-08)
Cloud Posse Reference Architecture
2024-08-01

Describe the Bug
The usage example defines two jobs: context
and atmos-plan
. The atmos-plan
job sets a “needs” dependency to atmos-affected
which doesn’t exist.
Expected Behavior
Either the context
job needs to be renamed to atmos-affected
, or the “needs” parameter needs to be updated to reference the context
job.
Steps to Reproduce
None.
Screenshots
No response
Environment
No response
Additional Context
No response

2024-08-08

README steps document automation cluster deployment as:
atmos workflow cluster/deploy -s core-usw2-auto -f eks
atmos workflow auto/deploy -f eks
The first should be deploy/cluster
I think. The second doesn’t seem to exist in the workflow (either as auto/deploy
or deploy/auto
). What are the workflow steps for auto/deploy
(or for deploy/auto
if the naming is reversed)?

@Jeremy G (Cloud Posse) @Jeremy White (Cloud Posse)
README steps document automation cluster deployment as:
atmos workflow cluster/deploy -s core-usw2-auto -f eks
atmos workflow auto/deploy -f eks
The first should be deploy/cluster
I think. The second doesn’t seem to exist in the workflow (either as auto/deploy
or deploy/auto
). What are the workflow steps for auto/deploy
(or for deploy/auto
if the naming is reversed)?

2024-08-09

Ah thanks for point that out; yes it’s a mistake. There are a few ways to deploy it, but the docs should say this 1 command to do it all:
atmos workflow deploy/github-runners -f github
This command will do everything you need:
- Provision service IAM roles for core-auto
- Deploy the core-auto EKS cluster
- Deploy all standard EKS resources
- Then finally deploy
eks/actions-runner-controller
Ultimately it’s the same as any other plat
EKS cluster, but for self-hosted runners we deploy eks/actions-runner-controller
after everything else is deployed

New docs are live! https://docs.cloudposse.com/
You can now access all the docs without registration.
The turnkey architecture for AWS, Datadog & GitHub Actions to get up and running quickly using the Atmos open source framework.

Very cool!
The turnkey architecture for AWS, Datadog & GitHub Actions to get up and running quickly using the Atmos open source framework.

I did find one page not found here https://docs.cloudposse.com/tags/setup/ which is linked from here https://docs.cloudposse.com/learn/ under “inside of each section”
It might help to use a broken link checker in the ci process

Yea, we still have a lot of broken links to resolve. We have have the broken link checker in warn mode.

Gotcha

Is there a formal release article for this ?

Not yet

cc @Dan Miller (Cloud Posse)

The get a jump start button also returns a 404

Can you DM me a screenshot

I have a PR with about a hundred fixed links and will be enforcing link checker once I get them all resolved

Sounds like Dans pr may fix the issue

That looks like a different issue, since that link should just go to cloudposse.com

Oh it does but cloudposse.com is dead

I cannot reproduce that

Im on mobile on 5g. I tried on firefox and brave with the same result


@Erik Osterman (Cloud Posse) I had this same issue 2 weeks ago and when we cleared cloudflare cache it fixed it

Hmm bizarre cause docs.cloudposse.com works fine for me

Ok, let me try that and see

try now

Still 404 for me, let me try a vpn

Wow, vpn worked

Idk now it works fine on and off the VPN


The best practices page’s next button loops to the same page
https://docs.cloudposse.com/best-practices/
Also no best practices show up here except for one elon musk quote

Our next priority is to relaunch cloudposse.com because of those weird issues. Moving from Wordpress to NextJS

Wow @Erik Osterman (Cloud Posse), this is just amazing news. Thanks so much for sharing all these rich resources with the world!
2024-08-10
2024-08-12
2024-08-13

Is there an adr available for deciding on opentofu vs terraform ?

@Igor Rodionov

@Andriy Knysh (Cloud Posse)

No, but we should have a design decision for it