#general (2024-12)

Hello, I am looking for some clarification on the automated cold-start documentation. It looks like the order of events is

• Review Design

• Prepare AWS Org

• Init TF backend

• Deploy Account Baseline

• Deploy Accounts But the “Deploy Account Baseline” (which precedes “Deploy Accounts”) starts with the text “Now that all accounts have been deployed” & we can an error that the account-map does not exist which is because we are working towards deploying accounts.

Based on this, should “Deploy Accounts” be before the baseline ?

Let’s keep self-promotion in #random and not this channel.

Breaking changes coming to GitHub Actions https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/

Anybody have to explain to their employer that they are using outdated methods and need to join the modern world? My team supports >2000 software developers in the financial industry and I’ve been tasked with helping to architect all the build jobs. I’m very familiar with DevOps and modern approaches. The problem is anytime I try to argue for what I think is basic best practice, sonar scans, shift left, automated testing, security scans in the build as vs just before a quarterly release, etc I’m met with confusion. As far as I can tell neither staff nor management understands these. They are very experienced, but very resistant to change. Thus they’ve (apparently) not been exposed to these ideas.

I want to “educate them” on these best practice: explain the benefits, the historical obstacles (industry wide) and what everybody else did to solve them. However I 1) Need it to be productive (complaining isn’t). 2) actually be able to present 10-20 years of process improvements SIMPLY enough to be effective.

…I can (am) googling these ideas but it’s awkward making an exhaustive list. 2) most of what I’m finding doesn’t give me the challenges to implementing them or the solutions companies used to get past them. For example DevSecOps should fail build with security issues, but that impacts developers for security issues that will be addressed before the production release later with a then-larger list. Even then, they get time to address it rather than do it in the next release.

Hi all, i’m heavily using provider maintained by Cloudposse team terraform-provider-utils , but it has few issues (not directly provider or Atmos) problem, but due upstream library used by Atmos tool. And, i would like to solve this issue by improving provider/Atmos instead of forking and using fork version. but it is sounds like nobody from primary maintainers actively following provider issues anymore. Is anyone else from Cloudposse team can help with it?

Hi, I’m preparing for AZ104 exam. Could anyone help me with preparation materials?