nebari-dev / nebari-dev/nebari-docs
[DOC] - Add FAQ about performing nebari deployments with huge version increments
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 21
- Forks
- 40
- Avg merge
- 19h 50m
- Merged PRs (30d)
- 6
Description
Preliminary Checks
- This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions
Summary
It might be convenient to include in our docs that while it's possible to run the nebari upgrade from the latest version available of nebari and directly deploy those terraform updates, since the maintainer team only supports incremental upgrades from the most recent previous version to the latest. We recommend that upgrades be done sequentially as well to avoid unforeseen circumstances.
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 by locating the Nebari upgrade documentation and any existing FAQ section. Add guidance that sequential upgrades are recommended and that maintainer support covers incremental upgrades from the most recent previous version; consider the work done when the recommendation and rationale are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- terraform
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100