All notable changes to this project will be documented in this file. The format loosely follows Keep a Changelog and the repository uses Semantic Versioning.
- New "Newman Testing Configuration" section in README documenting folder structure, file details, and step-by-step instructions for setting up Postman/Newman regression tests.
- New "How Environment Variable Injection Works" subsection explaining the
AIO_ENV_FILEmechanism and.envmaterialization flow. - Updated repository layout in README to include
tests/newman/folder structure.
- Added explicit
shell: bashto "Materialize branch .env file" step indeploy.yamlfor consistency with other shell steps.
- Workflow now consumes GitHub repository variables
ENV_STAGE/ENV_PROD, writes their full multi-line contents into.env, and feeds that file to the Adobe API Mesh CLI before create/update operations. - Documentation updates explaining the new
.envinjection path and the recommended GitHub variables for environment-specific configuration.
- New primary workflow
.github/workflows/deploy.yamlthat materializes branch-specific mesh secrets, computes CLI flags automatically, and waits for mesh provisioning with retry logic. - Reusable Newman regression workflow
.github/workflows/tests.yamlplus a dependenttestsjob so deployments can trigger API smoke tests per branch.
- Deployment job now emits
secrets.yamlat runtime from encrypted GitHub secrets (MESH_SECRETS_STAGE/MESH_SECRETS_PROD) to keep sensitive resolver credentials out of the repository. - Mesh commands (
aio api-mesh:create/update) automatically include--env .envand--secrets secrets.yamlwhen those files exist, reducing manual flag drift. - Mesh provisioning phase now polls
aio api-mesh:statuswith clearer logging and early-failure handling if the mesh never reaches a healthy state.
- Initial Adobe API Mesh CI/CD template with a GitHub Actions workflow for staging/production deployments, README-based setup guidance, and secret validation.
- Prebuilt runner image with
aio - no CLI installation steps in the workflow.