trufnetwork / trufnetwork/node
Problem: CI restarts the staging environment, but it should restart only the dev
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 3
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 13
Description
My suggestion:
- parameterize the CDK environment config
We have it hardcoded here and it is first used - stack name should depend on the environment
Otherwise, eachcdk deployof one environment will override the other.
I.e. Append the environment name here meaningTSN-DB-Stack-${environmentName} - change the CI process to use the new parameter to deploy using
DEVenvironment
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 with deployments/infra/cdk.json at line 64 and deployments/infra/config/config.go at lines 13 and 48 to trace how the environment is selected and how the stack name is built. Then inspect the CI deployment entry point that invokes CDK. Done means environments are parameterized, stack names include the environment, and CI deploys the DEV environment without overriding staging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100