Update the preflight and postrelease docs for starting a new release
branch and after publishing that release for the first time to update
the GitHub Action the scheduled building of the buildboxes.
Remove `.drone.yml` and `dronegen` which generates it from the repo,
disabling drone on master. Remove references to drone in docs.
The remaining piplines in `.drone.yml` were the tag build and promote
pipelines which now run on GitHub Actions, the push build pipelines that
are currently of limited value and will be re-done differently with a
little thought, and the `teleport-docker-cron-ecr` pipeline which no
longer works as of v15 due to the removal of the legacy OCI images (the
teleport-labs stuff that the pipeline builds is to be removed shortly
too).
From `docs/postrelease.md`:
- [x] Update `branchMajorVersion` const in Dronegen `/dronegen/container_images.go`, then run `make dronegen`
- [x] Update `CURRENT_VERSION_ROOT`, `PREVIOUS_VERSION_ONE_ROOT`, and `PREVIOUS_VERSION_TWO_ROOT` variables in `.drone.yml`, then run `make dronegen`
- Example: https://github.com/gravitational/teleport/pull/4602
- [x] Create PR to update default Teleport image referenced in docker/teleport-quickstart.yml
- Example: https://github.com/gravitational/teleport/pull/4655
- [x] Create PR to update default Teleport image referenced in docker/teleport-lab.yml
* Update docs version automatically
Adds a new job to the post-release workflow that automatically updates
the docs version when a new release is published.
Note: we do the plugin version as well, even though it's likely that
the teleport-plugins release is still outstanding. That's okay though,
we can wait to merge the PR if we want to.
Closes#12961
* Update postrelease docs
* Mention helm-unittest plugin version
There have been a number of incompatible forks and different versions
of this plugin. For now, ensure that the Makefile tells you exactly
what version you need to install.
* Mention GHA for updating AMIs post-release
Cam Hutchison