What problem are you facing?
The E2E tests currently install two Configuration packages. I imagine we'll have more in future.
|
package: us-west1-docker.pkg.dev/crossplane-playground/xp-install-test/configuration:main |
|
package: crossplane/e2e-depends-on-provider-nop:v0.1.0 |
One of these images is pulled from a private Google Artifact Registry. The credentials required to pull it don't grant access to anything else so we have them checked in in plaintext.
How could Crossplane help solve your problem?
I'd like to get these packages pushed to xpkg.upbound.io, probably in a new organization (crossplane-e2e?). This will get all our test dependencies:
- In one place, even if they need to be private. (Private Docker Hub listings cost us money.)
- In an org that makes it clear they're for E2E tests, not a "real" Crossplane thing.
Note that the package metadata is checked in under test/e2e/manifests, but there's no CI job that automatically builds and pushes these images at the moment. I don't think they change often enough that it's worth automating build/push.
What problem are you facing?
The E2E tests currently install two Configuration packages. I imagine we'll have more in future.
crossplane/test/e2e/manifests/pkg/configuration/private/configuration.yaml
Line 9 in 297f760
crossplane/test/e2e/manifests/pkg/configuration/dependency/configuration.yaml
Line 6 in 297f760
One of these images is pulled from a private Google Artifact Registry. The credentials required to pull it don't grant access to anything else so we have them checked in in plaintext.
How could Crossplane help solve your problem?
I'd like to get these packages pushed to xpkg.upbound.io, probably in a new organization (
crossplane-e2e?). This will get all our test dependencies:Note that the package metadata is checked in under
test/e2e/manifests, but there's no CI job that automatically builds and pushes these images at the moment. I don't think they change often enough that it's worth automating build/push.