#general - September 2020

Hey everyone, give a warm welcome to our newest members!
- @moos3
- @Ray Pasko
- @jtdoepke
- @Lior Rabin
- @Sehox
- @K H
- @Daniel Schopper
- @Paul Spurlock

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Cody Moore
- @Tayfun
- @stefan
- @Jeff Wozniak

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Alinafe Matenda
- @Repa Ferula

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @bigwheel k
- @U019ZRDCW1K
- @Maxime Sibellas
- @Jason
- @Denis Nguyen
- @Evgeni Enchev
- @Olha
- @Diamon
- @Jon Naglieri

Good to have you here =)

Do you guys have any documentation for setting up a cold start using the reference architectures?

I used it a year or so ago but cant seem to find the documentation around setting up an account from scratch

@Erik Osterman (Cloud Posse), gave variant2 a try today. Pretty cool, though definitely a huge difference from what I’m used to with powershell.
I see the biggest draw is all the the functions and effort in terraform are avialable. This means it already is starting with a huge library of well tested functions.

I think i’ll blog on this soon as i test further.
I had to write up a bash bootstrap script to download into my docker “codespaces”, so beyond that and lack of formatter right now it started to make sense.

job "deploy" {
    description = "Runs serverless command to deploy to AWS"

    option "bin_path" {
      type = string
      description = "The location of the build output for go build"
      default = "bin"

    }
    option "project_dir" { 
      type = string
      description = "build folder for the project"
      default = "functions/tacos"
    }

    exec {
        command = "serverless"
        dir = opt.project_dir
        env = {
            AWS_SDK_LOAD_CONFIG=1
            AWS_DEFAULT_REGION="eu-west-1"
            AWS_PROFILE="nonprod"
        }
        args = ["deploy"]
  }

variant run build

produced

vscode@codespaces_012633:~/workspace/devops-serverless$ variant run deploy
Serverless: Packaging service...
Serverless: Excluding development dependencies...
Serverless: Uploading CloudFormation file to S3...
Serverless: Uploading artifacts...
Serverless: Uploading service tacos.zip file to S3 (10.25 MB)...
Serverless: Validating template...
Serverless: Updating Stack...
Serverless: Checking Stack update progress...
.........
Serverless: Stack update finished...
Service Information
service: tacos
stage: dev
region: eu-west-1
stack: tacos-dev
resources: 6
api keys:
  None
endpoints:
  None
functions:
  tacoops: dev-tacocops
layers:
  None

Hey everyone, give a warm welcome to our newest members!
- @Obinna Ezeakachi
- @Mohammed Nazib

Good to have you here =)

Guys? Did You try to integrate https://github.com/siemens/sentry-auth-oidc to sentry? ( https://github.com/cloudposse/helmfiles/blob/master/releases/sentry.yaml ) Thanks

Hey everyone, give a warm welcome to our newest members!
- @Honza Novak
- @Manuele Fanelli
- @Chris Lavery

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @rmenn
- @Simon Emms
- @U01A91KSX5H
- @Alex Jurkiewicz

Good to have you here =)

Could someone help me work out what’s wrong with this nginx rule? ..

If I hardcode values in place of the $subdomain variable, it works.. But it doesn’t seem to like the interpolation that’s done here. It throws a 502 error… The header X-Subdomain-Proxy has the correct subdomain value in it.

server {
    server_name ~^(?<subdomain>.+)\.example\.com$;
    add_header X-Subdomain-Proxy $subdomain;
    location / {
        proxy_set_header Host $<http://subdomain.newdomain.com|subdomain.newdomain.com>;
        proxy_pass https://$<http://subdomain.newdomain.com|subdomain.newdomain.com>;
    }
}

Hey everyone, give a warm welcome to our newest members!
- @gugaiz
- @Sebastian Grateful
- @Aaron Miller
- @Adebayo Ogbagba
- @Corey Thomas

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Chris Warren
- @Andrew Red
- @Kelvin Tan
- @David Lundgren

Good to have you here =)

hello all, great to be here.

Hello everyone, just joined, looking forward for great new techi friends

Hey everyone, give a warm welcome to our newest members!
- @Rhenusone Rosalia
- @Ken Foreman
- @James Roller
- @Gabriel Tiossi
- @feixiaohuijava
- @Yash
- @Chien Huey
- @Sadbar Khattak

Good to have you here =)

👋 I’m here! What’d I miss?

Hey everyone, give a warm welcome to our newest members!
- @Angelo Pace
- @Steve P

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Vugar
- @Maciek Ciach

Good to have you here =)

Hello everyone !

Thank you guys! Glad to be here! 🙂

Hello everyone, just joined. I'm looking forward to migrate my workloads to using cloudposse's way.

Hey everyone, give a warm welcome to our newest members!
- @Marcin Cierpicki
- @Patrick Sodré
- @Matt Ryan

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Yen Kuo
- @ninja
- @Ashu
- @Varun penma
- @gusse
- @Vamshi Siddarth
- @Ben
- @Martin Canovas
- @João Ferreira
- @Michael Londeen
- @Vitalii Sikora
- @Sergey Pokatov

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Joaquin Menchaca
- @Iouns
- @Alex Taylor
- @Justin Seiser
- @Jones
- @James Villa

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Nesti

Good to have you here =)

Hello

Moin Moin

Moin ^^^

Hey everyone, give a warm welcome to our newest members!
- @Vedant Mhatre
- @Sweta
- @Jurgen
- @Majan Paul
- @Daniele P
- @Nitin Prabhu
- @rei
- @Jimmie Butler

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Tom
- @Alban
- @Dave Cobb

Good to have you here =)

👋 Hi folks ! thanks and happy to be here 🙂

Hey everyone, give a warm welcome to our newest members!
- @Stephen Bennett
- @Viacheslav Romanov

Good to have you here =)

https://github.com/docker/cli/issues/267#issuecomment-695149477 that's all you need to know about docker development speed 😄

Hello. Just looking to use https://github.com/cloudposse/terraform-aws-elasticache-redis. Part of the task is to create users on the redis server that are essentially read only users. Is this possible with this module, or terraform in general? We already have a bastion SSH tunnel in place that only allows tunnelling to specific destinations, so no issue with connecting to the redis instances.

My guess is that unless there's a specific resource to monitor, terraform isn't going to be involved.

But any suggestions would be appreciated.

Hey everyone, give a warm welcome to our newest members!
- @Kristoffer
- @Richard Quadling

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @vixus0
- @Viktor Farcic
- @Vasilios Tzanoudakis

Good to have you here =)

question for today: what is proper way of ensuring that kubectl command called in terraform (via local_exec) will succeed? I often (not all the time) find the command runs before the EKS cluster API server is ready so terraform aborts. If I re-run it again, that 10-20 seconds is sufficient for the server to be ready so terraform then completes the apply. I tried a few things, without success. Any docs on this would be awesome.

Hey everyone, give a warm welcome to our newest members!
- @Alex
- @Jay Zalowitz
- @Bob Strubel
- @Tomek
- @Charles Kim
- @Fernando Castillo

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Adin Hodovic
- @Smailli Moraes
- @Abhinav Khanna
- @rani
- @Denis Boulas

Good to have you here =)

Hello everyone 🙂

Hello! 🙂

Hey everyone, give a warm welcome to our newest members!
- @Lucio Zolezzi
- @Robbie Gladmon

Good to have you here =)

Hi guys!

anyone use buildkite here ?

Hey everyone, give a warm welcome to our newest members!
- @Mohammed Yahya
- @Eli Karchov
- @Peter Oates

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Aleix Conchillo Flaqué
- @1efty

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Venkata Pavan Kumar Varri
- @vroad
- @Solomon Tekle
- @Jihed Mselmi
- @aob-henry

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Didar Rashid
- @VJ

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Yasser Isa Manzur
- @jonjitsu
- @Tom Vaughan

Good to have you here =)

Thank you for terraform-aws-efs! I’m wondering what “namespace” does? I’m actually trying to create an EFS volume that can be accessed by pods in several namespaces. In “main.tf” I don’t see a reference to the namespace — is it there just for future expansion? … and will I be able to connect from mulitple namespaces? The internet is a little hazy on this. Thanks!