forked from datahub-project/datahub
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(cli): switch default quickstart to v0.10.0 (datahub-project#7567)
- Loading branch information
1 parent
18f387c
commit c656ed7
Showing
3 changed files
with
45 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,26 +1,39 @@ | ||
# if --version is specified during CLI run | ||
# the CLI will try to use the same docker-compose git ref and docker tags | ||
# --version v0.x.y will use the v0.x.y tag for all images and the compose file from the v0.x.y git tag | ||
# quickstart_version_map maps broken releases to fixed ones | ||
# key is the broken release | ||
# .composefile_git_ref: the git ref of the compose file to use | ||
# .docker_tag: the docker tag to use | ||
# if no version is specified the default key will be used | ||
# This file is used by the CLI to map quickstart version "labels" to docker tags and git refs. | ||
# It can also be used to override the defaults if master is broken, and to | ||
# map broken releases to fixed ones. | ||
# | ||
# in case of --version stable the latest released version will be used (by querying the github api) | ||
# the mapping for stable is not required, but can be used to override the latest release | ||
# If --version is specified during CLI run: | ||
# - If the version exists in this file, the details will be used. | ||
# - The handling of `stable` is special. See below. | ||
# - Otherwise, we'll assume that it represents a docker-compose git ref and docker tag. | ||
# e.g. `--version v0.x.y` will use the v0.x.y tag for all images and the compose file from the v0.x.y git tag. | ||
# - If no version is specified the "default" key will be used. | ||
# | ||
# This file can also be used to map broken releases to fixed ones. | ||
# key is the broken release | ||
# .composefile_git_ref: the git ref of the compose file to use | ||
# .docker_tag: the docker tag to use | ||
# | ||
# In case `--version stable` is specified AND the stable key is not defined here, | ||
# the latest released version will be used (by querying the github api) | ||
# As such, the mapping for stable is not required, but can be used to override the latest release. | ||
quickstart_version_map: | ||
# default key is mandatory and is used if no version is specified | ||
# in case of a broken release or broken master branch | ||
# specify a working version here | ||
# The "default" key is mandatory and is used if no version is specified. | ||
# In case of a broken release or broken master branch, specify a working version here. | ||
default: | ||
composefile_git_ref: fd1bd51541a132017a648f4a2f037eec8f70ba26 # v0.10.0 + quickstart compose file fixes | ||
docker_tag: v0.10.0 | ||
|
||
head: | ||
composefile_git_ref: master | ||
docker_tag: head | ||
# v0.9.6 images contain security vulnerabilities | ||
v0.9.6: | ||
|
||
# v0.9.6 images contain security vulnerabilities | ||
v0.9.6: | ||
composefile_git_ref: v0.9.6.1 | ||
docker_tag: v0.9.6.1 | ||
# if stable is not defined the latest released version will be used | ||
# stable: | ||
|
||
# If stable is not defined the latest released version will be used. | ||
# stable: | ||
# composefile_git_ref: master | ||
# docker_tag: head | ||
# docker_tag: head |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters