https://cloudposse.com logo
Join Slack
Powered by
hello, anyone able to confirm if planfile artifact...
# atmos
b
hello, anyone able to confirm if planfile artifact storage to gh artifacts has been implemented as of v1.221.1?
e
I think there is a documentation gap that we need to address. using the Artifacts API requires a little bit of trickery
I'll start a PR today
b
thank you, any chance the trickery is dump the planfile to local and then upload it with the artifacts action?
e
Maybe but that wasn't the design intent
That's the gist of it but heads up I've not yet reviewed this for AI slop
Copy code
# This is the entire reason github/artifacts works from a `run:` step.
      - name: Expose GitHub Actions runtime credentials
        uses: ./actions/github-runtime
        with:
          mode: env

      - name: Plan (uploads planfile to github/artifacts)
        working-directory: tests/fixtures/scenarios/native-ci
        run: atmos terraform plan mycomponent -s prod --ci
That's the key part of it. The issue is that the Artifacts API credentials are not available to Run Steps
So while Atmos natively supports interfacing with the Artifacts API, it can't do so in a run step without the credentials
So we have a GitHub action that you run that sets up the environment so that you can do it in a run step
But the CI failed so there's something else missing in the documentation or the workflow I will be able to look at that later on today at some point
b
got it, thank you for the thorough update
e
did you get it working?
b
no luck yet
e
Ok, stay tuned.
E2E tests with GHA workflows working in https://github.com/cloudposse/atmos/pull/2649
There were bug fixes associated with this so it will be included in the next release
If you want to give this a spin, it would help us merge it faster
b
I'll see what I can do to poke at it, will it show up in the next rc, or do I need to build it from the branch?
e
It will not show up in the next RC until we merge it
It should work if you set this ENV:
Copy code
ATMOS_USE_VERSION=2649
This will tell Atmos to download that artifact from this PR
And re-exec
b
that should work nicely, thank you Erik
e
Let me know if you were able to independently validate this
We did merge this into main so one of the recent release candidates should also have this code
It's taking us a while to cut the next release just because we are trying to make sure, as much as possible, everything is working end-to-end
b
not yet, I'm heads down on a heavy refactor to leverage JIT vendoring on as many of our components as we can, then I'll be back to refactoring workflows. I think one of my biggest boosts will be to switch to the atmos container instead of the cli + shell scripts we have all over our github workflows
🎉 1
3 Views
Open in Slack
PreviousNext
Powered by