Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ephemeral test environment #4069

Open
npalm opened this issue Aug 15, 2024 · 0 comments
Open

Ephemeral test environment #4069

npalm opened this issue Aug 15, 2024 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@npalm
Copy link
Member

npalm commented Aug 15, 2024

Problem

Merging PR's requires in most cases manual work. By deploying the PR and running a few test to check the change is working and not breaking the module. For the lambda's we have a good set of automated tests, but for the full module (including IaC) this is still missing.

Steps to test a change

In general, we test a change as follow.

  • set git ref to main
  • build lambda's
  • deploy examples. Typically mult-runner and or default (depending on the change)
  • point git to the PR
  • rebuild lambda's
  • deploy, main reason is to check the PR is not breaking a current deployment
  • run test based on a sample workflow and verify
  • destroy environment

Notes

  • Used Terratest back in the days for another project
  • Maybe new terraform test capabilites are an option
  • Having a script to run could be a good first step to automate
  • Challenge is how to ensure the AWS account remains safe when verifying PR's. Manual approval could be required.
  • Any help is welcome!
@npalm npalm added enhancement New feature or request help wanted Extra attention is needed labels Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant