almalinux/lorax
13
0
Fork 0
Code Issues Pull Requests Releases Activity
f33-branch
lorax/tests/pylorax/blueprints/example-kubernetes.toml

28 lines
374 B
TOML
Raw Permalink Normal View History

Add 'example' to the example blueprint names
2018-08-21 21:02:30 +00:00
name = "example-kubernetes"
Add the tests from lorax-composer branch These currently fail for several reasons and will be adjusted as the code it ported to this branch.
2018-04-30 18:34:48 +00:00
description = "An example kubernetes master"
Update the test blueprints Change versions to match Fedora versions. Add version numbers to the blueprints except for glusterfs.toml, not having a version is used as part of the tests.
2018-05-03 21:10:53 +00:00
version = "0.0.1"
Add the tests from lorax-composer branch These currently fail for several reasons and will be adjusted as the code it ported to this branch.
2018-04-30 18:34:48 +00:00
[[modules]]
name = "kubernetes"
tests: Use wildcard versions for packages Chasing updated package versions is silly. We already have other tests to make sure the blueprints support version numbers there is no need to fail a test at the whim of an upstream repo.
2019-12-10 22:10:57 +00:00
version = "*"
Add the tests from lorax-composer branch These currently fail for several reasons and will be adjusted as the code it ported to this branch.
2018-04-30 18:34:48 +00:00
[[modules]]
name = "docker"
tests: Use wildcard versions for packages Chasing updated package versions is silly. We already have other tests to make sure the blueprints support version numbers there is no need to fail a test at the whim of an upstream repo.
2019-12-10 22:10:57 +00:00
version = "*"
Add the tests from lorax-composer branch These currently fail for several reasons and will be adjusted as the code it ported to this branch.
2018-04-30 18:34:48 +00:00
[[modules]]
name = "docker-lvm-plugin"
tests: Use wildcard versions for packages Chasing updated package versions is silly. We already have other tests to make sure the blueprints support version numbers there is no need to fail a test at the whim of an upstream repo.
2019-12-10 22:10:57 +00:00
version = "*"
Add the tests from lorax-composer branch These currently fail for several reasons and will be adjusted as the code it ported to this branch.
2018-04-30 18:34:48 +00:00
[[modules]]
name = "etcd"
tests: Use wildcard versions for packages Chasing updated package versions is silly. We already have other tests to make sure the blueprints support version numbers there is no need to fail a test at the whim of an upstream repo.
2019-12-10 22:10:57 +00:00
version = "*"
Add the tests from lorax-composer branch These currently fail for several reasons and will be adjusted as the code it ported to this branch.
2018-04-30 18:34:48 +00:00
[[modules]]
name = "flannel"
tests: Use wildcard versions for packages Chasing updated package versions is silly. We already have other tests to make sure the blueprints support version numbers there is no need to fail a test at the whim of an upstream repo.
2019-12-10 22:10:57 +00:00
version = "*"
Add the tests from lorax-composer branch These currently fail for several reasons and will be adjusted as the code it ported to this branch.
2018-04-30 18:34:48 +00:00
[[packages]]
name = "oci-systemd-hook"
tests: Use wildcard versions for packages Chasing updated package versions is silly. We already have other tests to make sure the blueprints support version numbers there is no need to fail a test at the whim of an upstream repo.
2019-12-10 22:10:57 +00:00
version = "*"
Reference in New Issue Copy Permalink