lorax/tests/pylorax/blueprints/example-glusterfs.toml

name = "example-glusterfs"
description = "An example GlusterFS server with samba"

[[modules]]
name = "glusterfs"
version = "*"

[[modules]]
name = "glusterfs-cli"
version = "*"

[[packages]]
name = "samba"
version = "*"
Add 'example' to the example blueprint names 2018-08-21 21:02:30 +00:00			`name = "example-glusterfs"`
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 GlusterFS server with samba"`

			`[[modules]]`
			`name = "glusterfs"`
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 = "glusterfs-cli"`
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 = "samba"`
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 = "*"`