debian-forge-composer/test/data
Achilleas Koutsou b9098c64c4 test: add valid parent commit ID to test manifests
The previous value for parent was not a valid commit ID.  In a regular
compose request, the parent ref is resolved before being added as a
source in the manifest.  However, when building test manifests, since
the values aren't real, we don't resolve the ostree refs, meaning that
the test manifests weren't valid — they failed validity checks if run in
osbuild.

Replaced the fake parent ref with a fake parent commit ID
"ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff".
The manifests still aren't buildable, since they don't point to a valid
ostree repository or commit, but now they're at least valid (in the
technical sense).
2022-12-11 12:37:37 +00:00
..
ansible Firewall feature flag default value 2022-12-06 16:39:00 +01:00
azure Remove azure/main.tf file b/c not actually used 2022-10-24 10:16:01 +02:00
cloud-init tests: ship all tests in the -tests sub-package 2020-10-06 13:08:26 +02:00
composer test: extract common JTW code from the multi-tenancy.sh test 2022-08-04 11:55:43 +02:00
kerberos tests: ship all tests in the -tests sub-package 2020-10-06 13:08:26 +02:00
keyring tests: ship all tests in the -tests sub-package 2020-10-06 13:08:26 +02:00
koji test/koji: remove the koji-cli patch 2022-01-26 14:44:27 +01:00
manifests test: add valid parent commit ID to test manifests 2022-12-11 12:37:37 +00:00
repositories test: Use new CS9 repo built by PR#3136 2022-12-01 11:51:58 +01:00
testrepo test: add test repository metadata 2022-06-01 11:36:52 +01:00
upgrade8to9 tests/upgrade: copy shared_lib.sh to the test vm 2022-09-16 08:36:03 +02:00
worker test: extract common JTW code from the multi-tenancy.sh test 2022-08-04 11:55:43 +02:00
x509 test: generate certificates on fly instead of shipping them in the test RPM 2020-11-05 13:48:48 +01:00