provision.sh: ensure no repositories in the Service scenario
In the Service scenario, we should be testing that osbuild-composer works fine, without any repository configurations being present on the filesystem. Signed-off-by: Tomáš Hozza <thozza@redhat.com>
This commit is contained in:
parent
7437770352
commit
3607783339
1 changed files with 7 additions and 0 deletions
|
|
@ -57,7 +57,14 @@ sudo mkdir -p /etc/osbuild-worker
|
||||||
# interacting with cloud providers are configured directly in the worker. In addition,
|
# interacting with cloud providers are configured directly in the worker. In addition,
|
||||||
# no certificates need to be generated, because they are not used anywhere in this
|
# no certificates need to be generated, because they are not used anywhere in this
|
||||||
# scenario.
|
# scenario.
|
||||||
|
#
|
||||||
|
# Moreover, there should be no repositories configured in the Service scenario, because
|
||||||
|
# these are expected to be provided with the compose request.
|
||||||
if [[ "$AUTH_METHOD" != "$AUTH_METHOD_NONE" ]]; then
|
if [[ "$AUTH_METHOD" != "$AUTH_METHOD_NONE" ]]; then
|
||||||
|
# Remove the repositories, because it is not used in the Service scenario
|
||||||
|
sudo rm -rf /etc/osbuild-composer/repositories
|
||||||
|
sudo rm -f /usr/share/osbuild-composer/repositories/*
|
||||||
|
|
||||||
# Generate all X.509 certificates for the tests
|
# Generate all X.509 certificates for the tests
|
||||||
# The whole generation is done in a $CADIR to better represent how osbuild-ca
|
# The whole generation is done in a $CADIR to better represent how osbuild-ca
|
||||||
# it.
|
# it.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue