bottlerocket-os / bottlerocket-os/twoliter
Ability to change release start time and waves
- Dominant language
- Rust
- Stars
- 34
- Forks
- 43
- Avg merge
- 11h 13m
- Merged PRs (30d)
- 16
Description
When building a Bottlerocket repo, you call `cargo make repo`. If you don't want to use the [default wave schedule](https://github.com/bottlerocket-os/bottlerocket/blob/develop/sources/updater/waves/default-waves.toml), you also pass `-e PUBLISH_WAVE_POLICY_PATH=path`. If you want the wave schedule to start at a defined point in the future, you pass `-e RELEASE_START_TIME=RFC3339-or-offset`.
This call uses pubsys to create a new repo, or to update a repo given in your Infra.toml config file. However, once you've done so, the only way to change the start time or wave schedule is to create a new repo from scratch. It'd be nice to have the ability to update them in an existing repo. This is useful if your testing takes longer than expected, for example.
Contributor guide
Research direction
Start with the `cargo make repo` path and the pubsys handling described in the issue; inspect how `Infra.toml`, `PUBLISH_WAVE_POLICY_PATH`, and `RELEASE_START_TIME` are read. Trace the existing-repo update path and verify that both the release start time and wave schedule can be changed without recreating the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100