HI, what’s the tool you use for ECS deployment? with monitoring and rolebacks
Does anyone here use CircleCI to trigger terraform runs?
Also, is anyone here using TF Cloud / TF Enterprise?
I’m wondering how to have my circle jobs “wait” for terraform to complete, or check their status
Also trying to figure out how to detect which terraform files changed, if any, and perform a run in each …
Hello..I would soon be starting the same.. Have been running TF scripts via Jenkins so far. In CircleCi, I usually use
requires: in the
workflows: to have one build step wait on the other. Does that not work in your case ?
Are you using the TF remote executor ?
We use CircleCI for our deployments of EC2 infrastructure. Each stage is broken into its own step and run in its own docker container. So for example we run the plan step and pass the output tfplan to the next step which runs the apply step based off the plan output. We set this up by using the machine execution and call docker via a bash script to pass in TF_VAR variables.
There are CircleCI orbs out there that can do this for you and can help like this one > https://circleci.com/orbs/registry/orb/ngs/terraform
Hey guys, Faced the issue with CircleCI where it doesn’t have some static IPs to be whitelisted. Any suggestions on how to reach private AWS EKS endpoint out of CircleCI in order to do some k8s stuff?
we went with the bastion host option (our use case wasn’t EKS but rather RDS…but still applies)
CircleCI builds are currently run mainly from AWS East and West as well as Google Cloud Platform East. For this reason, we can not give a definitive list of IP addresses that our cloud system will …
Thank you @Darren Cunningham.
we combined that with the dynamic whitelisting…whitelist the executor IP, SSH to bastion, run commands and then remove the whitelisted IP
Ideally the CD platform you use supports the concept of “runners” where you can deploy it in the cluster and it tunnels out out. It doesn’t appear that CircleCI supports this.
You can host your own runners and customize the environment used to run jobs in your GitHub Actions workflows.
Cool. Thanks @Erik Osterman (Cloud Posse),
Didn’t use this
runners concept before.
Will go through the link you’ve provided and make myself familiar with it.
anyone know a good alternative to CircleCi? I know that @roth.andy is currently checking different options maybe you can share what you have found so far? I currently have to build a pipeline that has like 6 approval steps in sequence which results in super bad UX/DX on circleci’s UI.
I haven’t been using it for very long yet, but I’m incredibly happy so far with codefresh
codefresh is hosted on AWS right ?
I think so. They also offer an on-prem option though
it is just pain to get anything allowed for me that is hosted on AWS. But well might be worth the pain I will need to check it out.
(double check though, they could be on GKE too)
Or am I doing something horribly wrong here?
I have a provider that relies on resource provisioned by another resource so I split it up in two “layers” 01 and 02
and each terraform plan should be reviewed by an engineer
Codefresh looks like this.. you can have as many groups as you want
you can then stick the approval steps anywhere in the pipeline and have as many of them as you need
that looks MUCH nicer
@roth.andy has joined the channel
The GitHub Actions Runner is now open sourced. File issues and contribute to one of the most important components of GitHub Actions directly at: https://github.com/actions/runner The Runner is the application that runs a job from