#geodesic (2021-11)

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

Discussions related to https://github.com/cloudposse/geodesic Archive: https://archive.sweetops.com/geodesic/

2021-11-09

Mike Crowe avatar
Mike Crowe

Hey folks, I was looking back into geodesic and it appears things have changed. It looks like [root.cloudposse.co> is deprecated now, but <http://testing.cloudposse.co|testing.cloudposse.co](http://root.cloudposse.co) isn’t. However, the latter still references root in the instructions.

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

Oh yes, we have the public docs which are pretty up to date

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

Also, we have commercial docs for customers :-)

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

The testing repo still runs some of our automation

Mike Crowe avatar
Mike Crowe

Given root is obsolete now, how do you replace it? Also, you’ve deprecated aws-vault – what is suggested as the replacement?

Mike Crowe avatar
Mike Crowe

@Erik Osterman (Cloud Posse)?

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

What is deprecated is a foundational infrastructure spanning a dozen or more GitHub repos

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

Instead we moved to a mono repo approach

Mike Crowe avatar
Mike Crowe

Are there newer instructions about how to setup your account or how geodesic has changed?

2021-11-08

Andres avatar
Andres

Is there an upgrade path from the older variant based version to the current golang rewrite of Atmos?

1
Andres avatar
Andres

I have an existing project that has been using an older version of Atmos, I can’t tell which version but when I’m trying to build the project it appears to reference artifacts that no longer exist.

failed to get .variant files: stat: stat .variant2/cache/[email protected]_com_cloudposse_atmos.ref=master/atmos/modules/utils: no such file or directory

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

we’ll be working on README and help for the new atmos - all of that is missing

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

for now, this example is a complete working example that shows all the setup https://github.com/cloudposse/atmos/tree/master/examples/complete

atmos/examples/complete at master · cloudposse/atmos attachment image

Universal Tool for DevOps and Cloud Automation (works with terraform, helm, helmfile, istioctl, etc) - atmos/examples/complete at master · cloudposse/atmos

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)

and this is a command set that the new atmos supports

# CLI config
atmos version
atmos describe config

# Describe components and stacks
atmos describe component <component> -s <stack>
atmos describe component <component> --stack <stack>


# Generate
atmos terraform generate backend <component> -s <stack>
atmos terraform write varfile <component> -s <stack>   # this command will be changed to `terraform generate varfile`
atmos terraform write varfile <component> -s <stack> -f ./varfile.json  # supports output file


# Terraform
# (almost) all native Terraform commands supported
# <https://www.terraform.io/docs/cli/commands/index.html>
atmos terraform plan <component> -s <stack>
atmos terraform apply <component> -s <stack> -auto-approve
atmos terraform apply <component> -s <stack> --from-plan
atmos terraform deploy <component> -s <stack>
atmos terraform deploy <component> -s <stack> --from-plan
atmos terraform deploy <component> -s <stack> -deploy-run-init=true
atmos terraform workspace <component> -s <stack>
atmos terraform validate <component> -s <stack>
atmos terraform output <component> -s <stack>
atmos terraform graph <component> -s <stack>
atmos terraform show <component> -s <stack>
atmos terraform clean <component> -s <stack>


# Helmfile
# All native helmfile commands supported including [global options]
# <https://github.com/roboll/helmfile#cli-reference>
atmos helmfile diff <component> -s <stack>
atmos helmfile apply <component> -s <stack>

# Helmfile with [global options]
atmos helmfile diff <component> -s <stack> --global-options "--no-color --namespace=test"
atmos helmfile diff <component> -s <stack> --global-options="--no-color --namespace test"
1

2021-11-03

2021-11-02

Andres avatar
Andres

Hello, I’ve just come across the Atmos project, it looks great! I had a question which I couldnt find any details on. Is it possible to access the outputs of a components from another components?

The use case I see is, if I use a terraform module to create say an IAM role and then I need to use the output (arn) in a helm chart, is there an easy way to do that?

jose.amengual avatar
jose.amengual

yes, you can use the output

jose.amengual avatar
jose.amengual

a component is basically a terraform module

jose.amengual avatar
jose.amengual

you can use a single bucket for all the state and you can share the state too or use the outputs

Andres avatar
Andres

so I can use the terraform output as input to a helm variable? Do you know if there are some examples that show how thats done?

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

yes, look into how we use remote-state

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
terraform-aws-components/remote-state.tf at bd8bfc64305d92607701050b9060d23713798ab9 · cloudposse/terraform-aws-components attachment image

Opinionated, self-contained Terraform root modules that each solve one, specific problem - terraform-aws-components/remote-state.tf at bd8bfc64305d92607701050b9060d23713798ab9 · cloudposse/terrafor…

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

Here we look up the outputs from the vpc component

Andres avatar
Andres

within Terraform I understand, my question is more between terraform and helm… If I have a resource created in terraform, how do I use the output of that in helm? or do I have to wait till that is provisioned and then manually copy the output value into the var for the helm file

Andres avatar
Andres

I’m talking about Atmos specifically

jose.amengual avatar
jose.amengual

I do not think you can use tf outputs as helm inputs

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

so by design, we do not intend to make atmos do any form of interpretation of the values in stack configs

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

instead, make your components more declarative

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

e.g. if you need component a to use values from components b, then then make a read the outputs of b

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

if you have a helmfile that needs outputs from terraform, have terraform write your outputs to SSM, then read those values natively in your helmfiles which supports the awsssm notation

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

helm does not have the concept of outputs, hwoever the terraform helm provider has outputs, but those are not controlled by the user

Andres avatar
Andres

Thanks Erik, thats what I was looking for I hadn’t thought about using SSM for outputs. That will do the job

2021-11-01

    keyboard_arrow_up