pytest-docker-registry-fixtures

pytest-docker-registry-fixtures

Overview

Pytest fixtures to instantiate and populated local docker registries, using lovely-pytest-docker and docker-py, for testing.

Getting Started

Update setup.py to include:

from distutils.core import setup

setup(
	tests_require=["pytest-docker-registry-fixtures"]
)

All fixtures should be automatically included via the pytest11 entry point.

import requests
import pytest
from pytest_docker_registry_fixtures import DockerRegistryInsecure, DockerRegistrySecure  # Optional, for typing

@pytest.mark.push_image("busybox:1.30.1", "alpine")
def test_docker_registry_secure(docker_registry_secure: DockerRegistrySecure):
    response = requests.head(f"https://{docker_registry_secure.endpoint}/v2/",
        headers=docker_registry_secure.auth_header,
        verify=str(docker_registry_secure.cacerts),
    )
    assert response.status_code == 200

def test_docker_registry_insecure(docker_registry_insecure: DockerRegistryInsecure):
    response = requests.head(f"http://{docker_registry_insecure.endpoint}/v2/")
    assert response.status_code == 200

The push_image mark can optionally be added to stage images in the registry prior to testing. See Markers for details.

Installation

From pypi.org

$ pip install pytest_docker_registry_fixtures

From source code

$ git clone https://github.com/crashvb/pytest-docker-registry-fixtures
$ cd pytest-docker-registry-fixtures
$ virtualenv env
$ source env/bin/activate
$ python -m pip install --editable .[dev]

Fixtures

docker_client

Creates a Docker client using configuration values from environment variables. This fixture is used to replicate images into a registry.

from docker import DockerClient

def test_docker_pull(docker_client: DockerClient):
    image = docker_client.image.pull("busybox:1.30.1")

docker_registry_auth_header

Retrieves an HTTP basic authentication header that is populated with credentials that can access the secure docker registry service. The credentials are retrieved from the docker_registry_password and docker_registry_username fixtures. This fixture is used to replicate docker images into the secure docker registry service.

docker_registry_cacerts

Locates a user-defined CA trust store (tests/cacerts) to use to verify connections to the secure docker registry service. If one cannot be located, a temporary trust store is created containing certificates from certifi and the docker_registry_certs fixture. This fixture is used to instantiate the secure docker registry service.

docker_registry_certs

Returns the paths of the self-signed certificate authority certificate, certificate, and private key that are used by the secure docker registry service. This fixture is used to instantiate the secure docker registry service.

NamedTuple Fields

The following fields are defined in the tuple provided by this fixture:

• ca_certificate - Path to the self-signed certificate authority certificate.
• ca_private_key - Path to the self-signed certificate authority private key.
• certificate - Path to the certificate.
• private_key - Path to the private key.

Typing is provided by pytest_docker_registry_fixtures.DockerRegistryCerts.

docker_registry_htpasswd

Provides the path to a htpasswd file that is used by the secure docker registry service. If a user-defined htpasswd file (tests/htpasswd) can be located, it is used. Otherwise, a temporary htpasswd file is created using credentials from the docker_registry_password and docker_registry_username fixtures. This fixture is used to instantiate the secure docker registry service.

docker_registry_insecure

Configures and instantiates a docker registry without TLS or authentication.

import requests
from pytest_docker_registry_fixtures import DockerRegistryInsecure  # Optional, for typing

def test_docker_registry_insecure(docker_registry_insecure: DockerRegistryInsecure):
    for image_name in docker_registry_insecure.images:
        response = requests.head(
            f"http://{docker_registry_insecure.endpoint}/v2/{image_name.image}/manifests/{image_name.tag}",
        )
        assert response.status_code == 200
        assert "Docker-Content-Digest" in response.headers

NamedTuple Fields

The following fields are defined in the tuple provided by this fixture:

• docker_client - from docker_client
• docker_compose - Path to the fully instantiated docker-compose configuration.
• endpoint - Endpoint of the insecure docker registry service.
• endpoint_name - Endpoint of the insecure docker registry service, by service name.
• images - List of images that were replicated into the insecure docker registry service.
• service_name - Name of the service within the docker-compose configuration.

Typing is provided by pytest_docker_registry_fixtures.DockerRegistryInsecure.

docker_registry_password

Provides a generated password to use for authentication to the secure docker registry service. This fixture is used to replicate docker images into the secure docker registry service.

docker_registry_secure

Configures and instantiates a TLS enabled docker registry with HTTP basic authorization.

import requests
from pytest_docker_registry_fixtures import DockerRegistrySecure  # Optional, for typing

def test_docker_registry_secure(docker_registry_secure: DockerRegistrySecure):
    for image_name in docker_registry_secure.images:
        response = requests.head(
            f"https://{docker_registry_secure.endpoint}/v2/{image_name.image}/manifests/{image_name.tag}",
            headers=docker_registry_secure.auth_header,
            verify=str(docker_registry_secure.cacerts),
        )
        assert response.status_code == 200
        assert "Docker-Content-Digest" in response.headers

NamedTuple Fields

The following fields are defined in the tuple provided by this fixture:

• auth_header - from docker_registry_auth_header.
• cacerts - from docker_registry_cacerts.
• certs - from docker_registry_certs.
• docker_client - Docker client, from docker_client, with injected authentication credentials for the secure docker registry service.
• docker_compose - Path to the fully instantiated docker-compose configuration.
• endpoint - Endpoint of the secure docker registry service.
• endpoint_name - Endpoint of the secure docker registry service, by service name.
• htpasswd - from docker_registry_htpasswd
• images - List of images that were replicated into the secure docker registry service.
• password - from docker_registry_password.
• service_name - Name of the service within the docker-compose configuration.
• ssl_context - from docker_registry_ssl_context.
• username - from docker_registry_username.

Typing is provided by pytest_docker_registry_fixtures.DockerRegistrySecure.

docker_registry_ssl_context

Provides an SSL context containing the CA trust store from the docker_registry_cacerts fixture. This fixture is used to instantiate the secure docker registry service.

docker_registry_username

Provides a generated username to use for authentication to the secure docker registry service. This fixture is used to replicate docker images into the secure docker registry service.

pdrf_docker_compose_insecure

This fixture uses the docker_compose_files fixture to locate a user-defined docker-compose configuration file (typically tests/docker-compose.yml) that contains the pytest-docker-registry-insecure service. If one cannot be located, an embedded configuration is copied to a temporary location and returned. This fixture is used to instantiate the insecure docker registry service.

pdrf_docker_compose_secure

This fixture uses the docker_compose_files fixture to locate a user-defined docker-compose configuration file (typically tests/docker-compose.yml) that contains the pytest-docker-registry-secure service. If one cannot be located, an embedded configuration is copied to a temporary location and returned. This fixture is used to instantiate the secure docker registry service; however, unlike the configuration returned by the pdrf_docker_compose_insecure fixture, this configuration will be treated as a template; the $PATH_CERTIFICATE, $PATH_HTPASSWD, and $PATH_KEY tokens will be populated with the absolute paths provided by the docker_registry_certs and docker_registry_htpasswd fixtures, as appropriate.

Markers

pytest.mark.push_image

This marker specifies the docker image name(s) that should be replicated to the docker registry service(s) prior to testing. It can ...

... decorate individual tests:

import pytest
from pytest_docker_registry_fixtures import DockerRegistrySecure  # Optional, for typing

@pytest.mark.push_image("busybox:1.30.1", "alpine", "python,mysql:latest")
def test_docker_registry_secure(docker_registry_secure: DockerRegistrySecure):
	...

... be specified in the pytestmark list at the module level:

#!/usr/bin/env python

import pytest

pytestmark = [pytest.mark.push_image("busybox:1.30.1", "alpine", "python,mysql:latest")]

...

... or be provided via the corresponding --push-image command-line argument:

python -m pytest --push-image busybox:1.30.1 --push-image alpine --push-image python,mysql:latest ...

This marker supports being specified multiple times, and removes duplicate image names (see Limitations below).

A helper function, get_pushed_images, is included for test scenarios that wish to inspect the maker directly:

import pytest
from pytest_docker_registry_fixtures import DockerRegistrySecure, get_pushed_images, ImageName

@pytest.mark.push_image("busybox:1.30.1")
def test_docker_registry_secure(docker_registry_secure: DockerRegistrySecure, request):
    image_name = ImageName.parse(get_pushed_images(request)[0])

Enumerated Fixtures

It is possible to instantiate multiple registry instances using the corresponding enumerated fixtures. All fixtures listed above have _*list (e.g. docker_registry_secure -> docker_registry_secure_list) versions that will return enumerated lists of corresponding data type.

For example:

import requests
from typing import List  # Optional, for typing
from pytest_docker_registry_fixtures import DockerRegistrySecure  # Optional, for typing

def test_docker_registry_secure_list(docker_registry_secure_list: List[DockerRegistrySecure]):
    for docker_registry_secure in docker_registry_secure_list:
        for image_name in docker_registry_secure.images:
            response = requests.head(
                f"https://{docker_registry_secure.endpoint}/v2/{image_name.image}/manifests/{image_name.tag}",
                headers=docker_registry_secure.auth_header,
                verify=str(docker_registry_secure.cacerts),
            )
            assert response.status_code == 200
            assert "Docker-Content-Digest" in response.headers

It is possible to use both singular and enumerated fixtures within the same test context; however, the same values will be returned for the singular fixture as the first enumerated list value (i.e. docker_registry_secure == docker_registry_secure_list[0]). To avoid complications with lower layers, mainly docker-compose, and to allow for this interchangeability, caching is used internally.

By default, the scale factor of the enumerated instances is set to one (n=1). This value can be changed by overriding the pdrf_scale_factor fixture, as follows:

import pytest

@pytest.fixture(scope="session")
def pdrf_scale_factor() -> int:
    return 4

This fixture will be used to scale both the insecure and secure docker registries.

Limitations

• All the fixtures provided by this package are session scoped; and will only be executed once per test execution.
• The push_image marker is processed as part of the docker_registry_insecure and docker_registry_secure fixtures. As such:

• all markers will be aggregated during initialization of the session, and processed prior test execution.
• Pushed images will be replicated to both the insecure and secure docker registries, if both are instantiated.

• A working docker client is required to push images.
• At most 10 insecure and 10 secure docker registries are supported using the embedded docker compose.
• It is not currently possible to specify into which enumerated registry instances images should be replicated. As such, and for backwards compatibility, they will only be replicated into the first instance of each of the insecure and secure docker registries.

Development

Source Control