Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Problem: CI restarts the staging environment, but it should restart only the dev

Open
#188 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, go
Domain
cloud, devops, infrastructure

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.

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, each cdk deploy of one environment will override the other.
    I.e. Append the environment name here meaning TSN-DB-Stack-${environmentName}
  • change the CI process to use the new parameter to deploy using DEV environment
Dominant language
Go
Stars
7
Forks
3
Avg merge
3h 2m
Merged PRs (30d)
13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from trufnetwork/node

All issues in trufnetwork/node

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.