Files
Martin Atkins 4b8246c3ef e2etest: Install module packages with "oci" source address scheme
Following the lead of similar earlier work on testing the installation of
provider packages from OCI repositories, this new test exercises the new
OCI-based module source address syntax in an end-to-end fashion by directly
running "tofu init".

For the reasons described inline, this test uses a local test server as its
target OCI Registry and therefore needs to rely on a Go standard library
feature for overriding the trusted TLS certs which only works on Unix
systems other than macOS, and therefore this test will only run when the
e2etest suite is run on Linux systems. This matches the same compromise we
previously made for the provider installation flavor of this test, with
the same assumption that our module installer isn't doing anything
particularly platform-specific and that we're doing this in e2etest only
because that's an effective way to test that "package main" is wiring all
of the internal components together correctly.

Signed-off-by: Martin Atkins <mart@degeneration.co.uk>
2025-04-23 16:34:57 -07:00
..

This directory contains "image layout" directories, as described in this
specification:
    https://github.com/opencontainers/image-spec/blob/v1.0/image-layout.md

We use these in conjunction with the fake OCI registry implementation in
package fakeocireg as part of end-to-end testing the module installer's
"oci" source address scheme.

These fake repositories each contain valid metadata for some module packages,
though the module packages just contain placeholder configuration since this
is only intended for testing module package installation and not for testing
module evaluation.