#geodesic (2021-01)

geodesic https://github.com/cloudposse/geodesic

Discussions related to https://github.com/cloudposse/geodesic

Archive: https://archive.sweetops.com/geodesic/

2021-01-07

Andy Miguel (Cloud Posse) avatar
Andy Miguel (Cloud Posse)

hi all, we uploaded this video from a recent office hours episode, @Bill Clark reported having issues with the audio but I can’t reproduce. if anyone else can play it and lmk how it’s working that would be awesome, thanks!

Matt Gowie avatar
Matt Gowie

Seems to be working fine @Andy Miguel (Cloud Posse)

1
Bill Clark avatar
Bill Clark

I see this inconsistency when I look in the Dockerfile.options:# Our older Geodesic configurations relied on direnv, which we no longer recommend,# preferring YAML configuration files instead.ENV DIRENV_ENABLED=true

Bill Clark avatar
Bill Clark

Holy cow this Geodesic build is something else. Fingers-crossed this actually works for me! Brings me back to the gentoo linux days

Bill Clark avatar
Bill Clark

It worked! Very pretty ascii art!

2021-01-15

Michael Dizon avatar
Michael Dizon

hi all, just getting started with geodesic. managed to get the reference-architecture image built. i’m unsure of where to run make rootper the readme. also don’t see a configs directory in the repo, or the container

Michael Dizon avatar
Michael Dizon

interesting, looking at the repo — seems that the configs folder was deleted two years ago

Joe Niland avatar
Joe Niland

@Michael Dizon the reference-architecture is deprecated. I encourage you to check out https://github.com/cloudposse/atmos or Terragrunt.

cloudposse/atmos

Universal Tool for DevOps and Cloud Automation. Contribute to cloudposse/atmos development by creating an account on GitHub.

Joe Hosteny avatar
Joe Hosteny

@Joe Niland did you migrate your prior environment to use atmos and the new components? I’m curious if you did that, or started with fresh accounts?

cloudposse/atmos

Universal Tool for DevOps and Cloud Automation. Contribute to cloudposse/atmos development by creating an account on GitHub.

Joe Niland avatar
Joe Niland

@Joe Hosteny no, not yet. I’ll try it on the next client project for sure.

Joe Hosteny avatar
Joe Hosteny

Ah, thanks. I was hoping there was someone who went through this already. I have an existing org built on the old arch I’d like to port over.

Joe Niland avatar
Joe Niland

I will let you know if I get that opportunity. It could happen!

Michael Dizon avatar
Michael Dizon

@Joe Niland do you mean that you won’t be able to update the atmos repo until you use it on a project?

Joe Hosteny avatar
Joe Hosteny

I think he means that he is using the old reference architecture, and plans on using atmos with the new components only on new orgs / accounts for now

1
Michael Dizon avatar
Michael Dizon

@Joe Niland does this mean geodesic is also deprecated?

Joe Niland avatar
Joe Niland

No, not at all. Just the structure used for the multi-account Terraform project.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Ya geodesic is core to everything we do

1
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Atmos is just another tool we use and we use it in geodesic

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

But it can run anywhere

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

@Matt Gowie is working with us now to help with documentation.

Michael Dizon avatar
Michael Dizon

i’m trying to run the example in atmos. is there supposed to be a components folder in there?

Michael Dizon avatar
Michael Dizon

looks like there used to be one, but it was removed a little while ago

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Components are root modules

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Create your own or use ours

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Or both

Michael Dizon avatar
Michael Dizon

got it, i’ll look at it again in the morning or tonight if i get my second wind

Michael Dizon avatar
Michael Dizon

i had to add the account-map component to get it to run, but am now getting this error error configuring S3 Backend: IAM Role (arn:aws:iam::XXXXXXXX:role/eg-gbl-root-terraform) cannot be assumed.

Michael Dizon avatar
Michael Dizon

do i need to add something else?

Michael Dizon avatar
Michael Dizon

i checked the account, and the role doesn’t exist

Bill Clark avatar
Bill Clark

I don’t have the answer necessarily. But I think you need this piece as well: https://github.com/cloudposse/terraform-aws-iam-account-settings

cloudposse/terraform-aws-iam-account-settings

Terraform module to provision general IAM account settings - cloudposse/terraform-aws-iam-account-settings

1
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

@matt has just update that module to 0.14. We will update our AWS components to use it

1
Michael Dizon avatar
Michael Dizon

would this be replacing what currently exists in the account-settings directory?

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

No, I think we’re going to incorporate the module into that one

Michael Dizon avatar
Michael Dizon

ah okay thanks!

2021-01-16

2021-01-18

matt avatar
matt
07:40:03 PM

@matt has joined the channel

2021-01-20

    keyboard_arrow_up