510f091353
To w/a the missing a container rename feature of podman, implement renaming via removing of the original container and re-applying it from the same configs but using the new name. This fixes idempotency issues when service containers are executed under ephemeral names created via the paunch's unique containers names generator, while it is expected to have them executed under its wanted config names. Change-Id: If851604d25b6c7982d950bb9e13dceada3bfc161 Closes-Bug: #1805410 Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
10 lines
323 B
Plaintext
10 lines
323 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
pbr>=2.0.0,!=2.1.0 # Apache-2.0
|
|
|
|
cliff>=2.6.0 # Apache-2.0
|
|
tenacity>=3.2.1 # Apache-2.0
|
|
jmespath>=0.9.0 # MIT
|