Make Bundles name in dev similar to staging in production
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**:
When generating dev Bundles, always increase the number in the name: `bundles-2` -> `bundles-3`...
**Why is this needed**:
While debugging some of the e2e tests, we discovered that the `Bundles` object in dev (including `main` and release branches) always has the name `bundles-1`. That differs from staging and prod where each bundle has a monotonically increasing integer: `bundles-2` -> `bundles-3`...
This made validations like https://github.com/aws/eks-anywhere/pull/3346 difficult to write. Making dev Bundles have a naming scheme similar to the one for prod would allow us to have shared code for those validations as well and reducing the differences between how prod and dev work.
Contributor guide
Research direction
The issue concerns dev Bundles, including main and release branches, and compares their names with staging and production. No file or test is named, so start by locating the dev bundle-generation entry point and the existing staging/production naming behavior; verify the result against the e2e validation scenario referenced by PR #3346.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100