localstack-samples / localstack-samples/localstack-pulumi-samples
Add GitHub Actions workflow and Makefile for test automation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We should add a GitHub Actions workflow and a Makefile to automate running tests for individual Pulumi samples. These should be modeled after the existing workflows and Makefiles used in:
- localstack-samples/localstack-pro-samples/Makefile
- localstack-samples/localstack-pro-samples/.github/workflows/makefile.yml
Requirements:
- Create a top-level Makefile to run install, lint, start, stop, and test commands for each Pulumi sample directory (similar to pro-samples).
- Add a GitHub Actions workflow under
.github/workflows/to run CI tests for all samples, similar to the referenced pro-samples workflow. - Ensure the workflow installs dependencies, sets up LocalStack, pulls the Docker image, and executes tests using the Makefile.
- Link to relevant references for implementation:
This will keep testing consistent across all LocalStack sample repositories and simplify maintenance.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the referenced pro-samples Makefile and .github/workflows/makefile.yml, then inspect the Pulumi sample directories in this repository. Add the requested top-level Makefile and workflow under .github/workflows/. Done means the workflow installs dependencies, sets up LocalStack, pulls the Docker image, and runs tests for all samples through the Makefile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, python
- Domain
- build-system, ci-cd, devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100