liquidmetal-dev / liquidmetal-dev/flintlock
Re-write e2e infra provisioning
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
Right now there is some dodgy, almost-works-if-you-dont-touch-it python tooling, but terraform would probably make it less unwieldy to use.
We have some modules [here](https://github.com/weaveworks-liquidmetal/terraform-equinix-liquidmetal), which could be refactored to serve as a base. Using those existing modules would not work as the flint tests need a different setup from a full LM solution.
Contributor guide
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 locating the existing Python e2e infrastructure provisioning tooling and documenting how the Flint tests currently use it. Review the linked terraform-equinix-liquidmetal modules as a possible base, while comparing their setup with the setup required by Flint tests. Done means the e2e infrastructure is provisioned through a maintainable Terraform-based setup tailored to those tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, terraform
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100