Skip to content

Generate e2e/.env from up.sh and fix SAC deploy error#27

Merged
AquiGorka merged 1 commit intomainfrom
fix/e2e-env-and-sac-deploy
Mar 20, 2026
Merged

Generate e2e/.env from up.sh and fix SAC deploy error#27
AquiGorka merged 1 commit intomainfrom
fix/e2e-env-and-sac-deploy

Conversation

@AquiGorka
Copy link
Copy Markdown
Contributor

Summary

  • up.sh now writes contract IDs, provider URL, and keys to e2e/.env after deploying contracts — E2E tests no longer need to know the provider-platform repo path
  • Fixes E2E on machines using non-default repo locations (BASE_DIR=~/projects)
  • e2e/config.ts now checks local e2e/.env before falling back to provider-platform's .env
  • Fixed SAC deploy failing under set -e when the contract already exists on a persistent Stellar network (changed || fallback to if/else)
  • Added e2e/.env to .gitignore

Test plan

  • Run ./up.sh — verify e2e/.env is generated with correct contract IDs
  • Run cd e2e && deno task e2e — should load config without errors
  • Run ./up.sh a second time (SAC already deployed) — should not error

up.sh now writes contract IDs, provider URL, and keys to e2e/.env so
the E2E test works without knowing the provider-platform repo path.
This fixes E2E on machines using non-default repo locations (BASE_DIR).

Also fixed SAC deploy failing under set -e when the contract already
exists on a persistent Stellar network.
@AquiGorka AquiGorka merged commit 44109c5 into main Mar 20, 2026
1 check passed
@AquiGorka AquiGorka deleted the fix/e2e-env-and-sac-deploy branch March 20, 2026 18:22
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