Add a profile that configures test fixtures

[lubosmj]

[noissue]

[lubosmj]

Does oci_env have any facility for running remote fixtures locally? Something like we do have in pulp_installer: the pfixtures command. If yes, then I would need to add some workflows for updating REMOTE_FIXTURES_ORIGIN accordingly.

[mdellweg]

Does oci_env have any facility for running remote fixtures locally? Something like we do have in pulp_installer: the pfixtures command. If yes, then I would need to add some workflows for updating REMOTE_FIXTURES_ORIGIN accordingly.

Sounds like a profile could add the fixtures container to the pod.

[lubosmj]

I am not able to verify these changes. Any volunteer?

[decko]

I am not able to verify these changes. Any volunteer?

Any instructions on how to test it?

[lubosmj]

First, you add COMPOSE_PROFILE=pfixtures to compose.env, initialize the environment, and then you can try running tests which rely upon fixtures from https://fixtures.pulpproject.org/ (pulp_rpm, pulp_deb, pulp_python?). These fixtures should be now accessible locally. Therefore, you can disable the internet connection for the time the tests are running.

[mdellweg]

Can we thing about the name of the profile? The name pfixtures was chosen in accordance with the other p* helper commands. I would prefer "local_fixtures" if that is not too long.

[lubosmj]

I updated the name of the profile and tested the changes on the pulp_rpm/.../test_sync.py tests. 👌🏻