Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add registry and owner parameters to Image #550

Closed
wants to merge 3 commits into from

Conversation

DDtKey
Copy link
Collaborator

@DDtKey DDtKey commented Feb 18, 2024

It's alternative solution for #549
A bit more user-friendly because operates with separate entities, but kinda redundant. Instead of configuring 1 parameter to override, users will have to split it to 3.

E.g: gallery.ecr.aws/docker/library/redis should be represented as:

  • registry: gallery.ecr.aws
  • owner: docker/library
  • name: redis

But user actually can just pass gallery.ecr.aws/docker/library/redis to name, or gallery.ecr.aws/docker/library to owner. We can't protect it.

Adds ability to set registry and owner on per-Image basis, and override them with RunnableImage.

Closes #335

This change allows to override name of the image. Thus, user will be able to change registry, owner and the name itself.

Closes testcontainers#335
It's alternative solution for testcontainers#549

Adds ability to set registry and owner on per-Image basis, and override them with `RunnableImage`.
@DDtKey DDtKey marked this pull request as draft February 18, 2024 19:17
@DDtKey DDtKey closed this Apr 6, 2024
@DDtKey DDtKey reopened this Apr 6, 2024
@DDtKey DDtKey closed this Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow custom docker registry
1 participant