atmos-dev
654,559
Discuss atmos core development (golang). If you want to help out, reach out to @Erik Osterman (Cloud Posse)
erik1 day ago
@Andriy Knysh (Cloud Posse) this adds "Try it" examples anywhere we have one. Users can easy try examples locally, no manual cloning required.
github.com/cloudposse/atmos/pull/3447
github.com/cloudposse/atmos/pull/3447
erik2 days ago
We surpassed 86% test coverage! Raising the bar to 90% 😃
Jorrit Elfferich2 days ago(edited)
Hey folks. Something is off, it's probably a timing issue somewhere in the release pipelines:
• The tagged 1.233.0 release points to the git tag
• The release assets added to that release, point to
One-liner to check the sha on the release binary:
whereas:
• The tagged 1.233.0 release points to the git tag
v1.233.0 which points to 12f83b5.• The release assets added to that release, point to
b392e54f7, which is 3 commits before 12f83b5. One-liner to check the sha on the release binary:
d=$(mktemp -d) && gh release download v1.233.0 -R cloudposse/atmos -p atmos_1.233.0_darwin_arm64 -D "$d" && go version -m "$d/atmos_1.233.0_darwin_arm64" | grep vcs.revision; rm -rf "$d"
build vcs.revision=b392e54f74a9c436d2c27fc8ba1b82605e95b58ewhereas:
git ls-remote <https://github.com/cloudposse/atmos> refs/tags/v1.233.0
12f83b5248253662d8af06030e3966034a7ef5d4 refs/tags/v1.233.0erik2 days ago
@Andriy Knysh (Cloud Posse) I can't approve this since I pushed a fix; it was failing in merge queue github.com/cloudposse/atmos/pull/3381
erik2 days ago(edited)
@Andriy Knysh (Cloud Posse) when tests finish we're ready to cut 1.233.0 github.com/cloudposse/atmos/pull/3434
these were the only regressions that GPT Astra 6 and Fable 5.1 were able to find relative to 1.232.0
these were the only regressions that GPT Astra 6 and Fable 5.1 were able to find relative to 1.232.0
erik3 days ago
@Andriy Knysh (Cloud Posse) github.com/cloudposse/atmos/pull/3403 (5 PRs in stack - implements atmos policies)
After this we're "ready for release", but I want to still run some regression tests after this stack merges
After this we're "ready for release", but I want to still run some regression tests after this stack merges
erik3 days ago
@Andriy Knysh (Cloud Posse) documentation update github.com/cloudposse/atmos/pull/3419
erik3 days ago
@Andriy Knysh (Cloud Posse) this PR stack is ready - updates docs
github.com/cloudposse/atmos/pull/3409
github.com/cloudposse/atmos/pull/3418
github.com/cloudposse/atmos/pull/3409
github.com/cloudposse/atmos/pull/3418
erik4 days ago
Pro tip, you can run
/goal quality-gate approved to get your PRs merge readyerik4 days ago
@Andriy Knysh (Cloud Posse) this adds a new
github.com/cloudposse/atmos/pull/3395
!ci.labels function useful for using CI context as part of stack configuration (e.g. stack metadata like tags, labels )github.com/cloudposse/atmos/pull/3395
erik4 days ago
@Andriy Knysh (Cloud Posse) this introduces a
github.com/cloudposse/atmos/pull/3405
/regression-test skill as a compliment to the /field-test skill; it specifically tests the current checkout against the previous release and identifies the subtle, unintended changes in behavior. While the field-test skill focuses on finding bugs, this skill focuses on finding bugs relative to the previous release.github.com/cloudposse/atmos/pull/3405
erik4 days ago
@Andriy Knysh (Cloud Posse) this introduces
github.com/cloudposse/atmos/pull/3392
The
atmos doctor and atmos doctor --fix which can diagnose many problems, and fix certain deprecations, etc.github.com/cloudposse/atmos/pull/3392
The
doctor command is a common function these days in advanced CLIs.erik4 days ago(edited)
@Andriy Knysh (Cloud Posse) github.com/cloudposse/atmos/pull/3404 I realized we didn't finish supporting full templating of terraform docs in
atmos docserik6 days ago
@toka btw, we merged the starlark implementation; it's in main
toka6 days ago
Hey guys! First time contributing here, so forgive me if I missed a step. I opened github.com/cloudposse/atmos/pull/3397 with a fix for bulk
terraform deploy skipping planfile verification (issue: github.com/cloudposse/atmos/issues/3396).erik7 days ago
@Andriy Knysh (Cloud Posse) github.com/cloudposse/atmos/pull/3388 (adds social cards for links when shared)
erik8 days ago
@Andriy Knysh (Cloud Posse) github.com/cloudposse/atmos/pull/3383 one more fix for quality gate; iti wasn't working for forks
Jorrit Elfferich8 days ago
Hey folks, saw this gap which I didn't expect, decided to plug it 👀. Keen on your thoughts!
github.com/cloudposse/atmos/pull/3381
github.com/cloudposse/atmos/pull/3381
erik8 days ago
@Andriy Knysh (Cloud Posse) one more trying to tune the quality gates https://github.com/cloudposse/atmos/pull/3376
erik10 days ago
@Andriy Knysh (Cloud Posse) one more fix for the quality gates github.com/cloudposse/atmos/pull/3367
erik11 days ago
@Andriy Knysh (Cloud Posse) github.com/cloudposse/atmos/pull/3356 this is to catch future performance regressions; it also introduces an aggregate quality gate, to make it easier for contributors to know what required
PePe Amengual13 days ago(edited)
has there been reports of describe affected slowing down 40x on 1.231.0?
erik13 days ago
@Andriy Knysh (Cloud Posse) github.com/cloudposse/atmos/pull/3347 many PRs are failing due to a bug in govulncheck's SARIF output
erik14 days ago
I moved CloudFormation and Scripting PR stacks out of 1.231.0 to 1.232.0
erik14 days ago
@Andriy Knysh (Cloud Posse) after this we can cut the release github.com/cloudposse/atmos/pull/3316