PostgREST / PostgREST/postgrest-benchmark
Can't use newer AWS instances
Open
Nobody has claimed this yet.
bug
- Dominant language
- Nix
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Problem
Specifying AWS instances like the t4g series fail on NixOps.
Proposal 1
Update NixOps. Not sure if this will solve it as NixOps status is unclear https://github.com/NixOS/nixops/issues/1574.
Proposal 2
Switch to terranix?
Proposal 3
Use plain terraform?
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 reproducing the failure when specifying a t4g AWS instance through NixOps, then review the linked NixOps issue 1574. Compare updating NixOps with switching to terranix or plain Terraform; done means the benchmark can provision and use newer AWS instance types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, terraform
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100