Skip to content

ci: Auto-export sourced provider env in regression-env-apply - #151

Merged
samir-gandhi merged 1 commit into
mainfrom
fix/regression-env-apply-cleanup
Sep 21, 2026
Merged

samir-gandhi merged 1 commit into
mainfrom
fix/regression-env-apply-cleanup

Conversation

@samir-gandhi

Copy link
Copy Markdown
Contributor

Summary

  • Second dispatch (run 35563160568) got past the file-lifetime fix but failed at terraform init with No valid credential sources found for the S3 backend.
  • Root cause: the TERRAFORM_PROVIDER_ENV_BASE64 payload is dotenv-style (AWS_ACCESS_KEY_ID=..., no export). Sourcing it with . file sets shell variables but does not export them — the terraform subprocess inherited nothing.
  • Fix: source with set -a / set +a in the Terraform init and Terraform plan steps so all sourced vars (AWS, PINGONE, TF_VAR_*) are auto-exported.

Test plan

  • YAML parses
  • Failure reproduced on run 35563160568 (backend init found no credentials)
  • Re-dispatch mode=plan after merge — init should reach the S3 backend and plan should report the environment state

🤖 Generated with Claude Code

The TERRAFORM_PROVIDER_ENV_BASE64 payload is dotenv-style (VAR=...,
no export statements). Sourcing it set shell variables only — the
terraform subprocess never inherited AWS_*/PINGONE_*/TF_VAR_*, so the
S3 backend failed with "No valid credential sources". Source with
set -a/set +a in both the init and plan steps so every sourced var is
exported.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@samir-gandhi
samir-gandhi merged commit c6284bd into main Sep 21, 2026
7 checks passed
@github-actions

Copy link
Copy Markdown

Regression Test Results

Matrix Entry Status Breaking Acceptable
default-hcl ✅ PASS 0 0
default-tfjson ✅ PASS 0 0
hcl-include-all ✅ PASS 0 0
hcl-skip-deps ✅ PASS 0 0
tfjson-skip-deps ✅ PASS 0 0

✅ No regressions detected

All export configurations produced compatible output.


Generated by regression workflow • View run

@samir-gandhi
samir-gandhi deleted the fix/regression-env-apply-cleanup branch September 22, 2026 02:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant