#release-engineering (2019-05)

jenkins_ci All things CI/CD. Specific emphasis on Codefresh and CodeBuild with CodePipeline.

CI/CD Discussions

Archive: https://archive.sweetops.com/release-engineering/

2019-05-08

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

we are on now

cabrinha avatar
cabrinha

cant talk but will listen

2019-05-06

cabrinha avatar
cabrinha

What is the go-to or standard approach to SDLC for infrastructure code?

cabrinha avatar
cabrinha

Anyone got some articles/docs? I’m also wondering what CloudPosse uses and suggests.

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

@cabrinha i don’t have it written down, but have lots and lots to say about it

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

if you want to join this wednesday office hours at 11:30 am

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

i’ll share

cabrinha avatar
cabrinha

i’ll try to make it to that, let me know if you throw a blog post out there in the meantime

2019-05-04

evgmoskalenko avatar
evgmoskalenko

Thanks)))

2019-05-03

evgmoskalenko avatar
evgmoskalenko

Hello, Could you tell me please, how are you deploy services to the AWS? Just describe by Terraform the infrastructure in a separate repository?

evgmoskalenko avatar
evgmoskalenko

Or describe the service in Terraform and put terraform code in the repository of the service?

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

@evgmoskalenko usually #1 - describe infrastructure in a separate repo. We do multi-account setup, one AWS account per environment (prod, staging, dev, testing etc.). Each environment/account is represented by a GitHub repo, which usually provides all the variables (from Dockerfile, ENV vars, TF vars, etc.)

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

take a look here:

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)
cloudposse/reference-architectures

Get up and running quickly with one of our reference architecture using our fully automated cold-start process. - cloudposse/reference-architectures

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

All TF code is in one central catalog that is reused across all repos https://github.com/cloudposse/terraform-root-modules

cloudposse/terraform-root-modules

Example Terraform service catalog of “root module” blueprints for provisioning reference architectures - cloudposse/terraform-root-modules

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)
cloudposse/root.cloudposse.co

Example Terraform Reference Architecture for Geodesic Module Parent (“Root” or “Identity”) Organization in AWS. - cloudposse/root.cloudposse.co

Andriy Knysh (Cloud Posse) avatar
Andriy Knysh (Cloud Posse)
cloudposse/prod.cloudposse.co

Example Terraform/Kubernetes Reference Infrastructure for Cloud Posse Production Organization in AWS - cloudposse/prod.cloudposse.co

    keyboard_arrow_up