https://cloudposse.com logo
Join Slack
Powered by
Am I missing it or does the latest default geodesi...
# geodesic
j
Am I missing it or does the latest default geodesic image not include atmos? I see the tutorial image added it in it's Dockerfile. If that's the case then I assume I just need to generate my own custom image.
a
this is what we do in Dockerfile
Copy code
ARG VERSION=0.147.11
ARG OS=debian
ARG ATMOS_VERSION=1.3.17

FROM cloudposse/geodesic:$VERSION-$OS

# Install atmos (<https://github.com/cloudposse/atmos>)
ARG ATMOS_VERSION
RUN apt-get update && apt-get install -y atmos="${ATMOS_VERSION}-*"
j
Okay so you do just build another image off the cloudposse/geodesic base image. Easy enough
a
yes we do
the Dockerfile is in each infrastructure repo
j
oh okay... the infrastructure repo
as in the archive *.cloudposse.co repos?
a
that’s very old. We usually create 
infrastructure
repo with all the stacks and components in it, then in the Dockerfile we use the code above. Same structure as in https://github.com/cloudposse/atmos/tree/master/examples/complete + the Dockerfile
j
yeah I thought I'd heard Erik say the *.cloudposse.co was old and used envdir that was no longer your recommended way. I hadn't looked at geodesic or atmos previously until it was discussed during the office hours this week
a
we use both in all client engagements (
atmos
is lacking good docs, we are working on it)
j
I liked the functionality with the first blush exposure during the zoom call. I've been looking at how to restructure my workflow going forward. I'd already been moving everything to Terraform and getting away from manual changes. Though I was still using Terraform Cloud for remote state
e
Some live tutorials here
these are more current
j
@Erik Osterman (Cloud Posse) I was actually running through that repo and executing them and ran into issues with the AWS environment example and the s3-cdn module
e
can you share the error?
j
the fix there allowed the plan to succeed and apply but the end result was not visible using the cloudfront distribution. I suspect due to changes in S3/cloudfront and the policy assigned via the s3-cdn module without extra values being set
e
aha, I think this is actually changes in the AWS provider
j
Yeah that's possible
2 Views
Open in Slack
PreviousNext
Powered by