Would love feedback on this upcoming atmos feature: native CI integration in atmos without using `cloudposse/github-action-atmos-*`; • Status checks API (so you can create merge requirements) • PR commments (templated and configurable) • Job summaries (same) • matrix generation •

GITHUB_OUTPUT

- use terraform ouputs between jobs • pluggable, so adapters can be written for Gitlab/ADO/etc

@Erik Osterman (Cloud Posse) if I'm understanding this correctly, the goal is to make an enhancement for CI that is platform-agnostic? So even though CloudPosse's "go-to" is GHA, this will essentially open the door to other CI solutions including, but not limited to: • Bitbucket Pipelines • Jenkins • CircleCI

Yes, precisely. It exposes a an interface that can be extended to other providers. We will implement GHA, and community can contribute others. But the invocation of atmos does not change; just the configuration.

Right now, my team uses Bitbucket for SCM and Jenkins for CI. Right now, one of our biggest issues is the lack of transparency between Bitbucket and Jenkins. It wasn't until recently we sorted out how to implement Bitbucket Pull Request Comments Reporter for MegaLinter - MegaLinter by OX Security into our existing Jenkins library to post SAST results into the PRs.

Mid Jan. Initial implementation is there, will start to validate week after next.

@Esteban Angee food for thought ^^

Do you need a hand in "GCS store planfile storage"? Looking forward to eliminate the need of

cloudposse/github-action-atmos-*

in our CI.

Yes, that would be great @shirkevich

how should I approach this? should I wait for your branch to be merged? or create on top of it and create PR to your branch?

Note that @Igor Rodionov has his own branch with a lot of fixes

ok, ping me pls when you ready