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: Support private registry host #28

Merged
merged 4 commits into from
Mar 10, 2019
Merged

feat: Support private registry host #28

merged 4 commits into from
Mar 10, 2019

Conversation

prehnRA
Copy link
Contributor

@prehnRA prehnRA commented Feb 16, 2019

This pull request adds support for non-default docker hosts (such as self-hosted registries or services like Amazon ECR). It introduces an optional environment variable DOCKER_REGISTRY to denote the URL of the registry. If this variable is left blank, the default registry of the docker client (probably Docker Hub) will be used.

* feat: Support login to private registry

* chore: Prettify lib/verify.js

* fix: Use DOCKER_REGISTRY instead of DOCKER_HOST to avoid conflict
@prehnRA
Copy link
Contributor Author

prehnRA commented Feb 21, 2019

@felixfbecker Thank you for this package. Is there anything I can do to make this pull request able to be merged?

Copy link
Owner

@felixfbecker felixfbecker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I missed this PR

lib/verify.js Outdated Show resolved Hide resolved
* feat: Support login to private registry

* chore: Prettify lib/verify.js

* fix: Use DOCKER_REGISTRY instead of DOCKER_HOST to avoid conflict

* fix: Switch registry URL to config

* fix: Change capitalization of config to match other configs

* chore: Make documentation for registryUrl more specific
@guibernardino
Copy link

+1

@prehnRA
Copy link
Contributor Author

prehnRA commented Mar 8, 2019

@felixfbecker Do the changes here work for you? Or do you have any additional feedback I can address?

README.md Outdated
@@ -27,9 +30,9 @@ Set of [semantic-release](https://github.com/semantic-release/semantic-release)

## Configuration

Your credentials have to be configured with the environment variables `DOCKER_USERNAME` and `DOCKER_PASSWORD`.
Your credentials have to be configured with the environment variables `DOCKER_USERNAME` and `DOCKER_PASSWORD`. If you are using a private docker registry, set its URL in the environment variable `DOCKER_REGISTRY`.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not correct anymore, right?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it still is. I looked at the beta api of semantic-release plugins and it seems unchanged. But a lof of things have been added to the beta release (channels etc.).

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I meant the DOCKER_REGISTRY env var, I don’t see that used anymore

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@felixfbecker Oops. You are correct. I forgot to take out the old change to the docs when I put in the new one. I just fixed that.

@felixfbecker felixfbecker merged commit b4fd322 into felixfbecker:master Mar 10, 2019
@felixfbecker
Copy link
Owner

🎉 This PR is included in version 2.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

JoA-MoS pushed a commit to semantic-release-plus/semantic-release-docker that referenced this pull request Aug 6, 2020
This pull request adds support for non-default docker hosts (such as self-hosted registries or services like Amazon ECR). It introduces an optional environment variable DOCKER_REGISTRY to denote the URL of the registry. If this variable is left blank, the default registry of the docker client (probably Docker Hub) will be used.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants