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

Allow insecure and/or anonymous registry #29

Merged
merged 4 commits into from
Nov 26, 2019
Merged

Allow insecure and/or anonymous registry #29

merged 4 commits into from
Nov 26, 2019

Conversation

c0va23
Copy link
Contributor

@c0va23 c0va23 commented Nov 25, 2019

Hi, I have implemented support for insecure registries. Similar to "plugins/docker".

I also added the possibility of anonymous access to the registry.

I also updated manifest-tool to version 1.0.0, because starting from this version there is support for insecure registries.

@lafriks lafriks added the enhancement New feature or request label Nov 25, 2019
Copy link
Contributor

@tboerger tboerger left a comment

Choose a reason for hiding this comment

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

Have you checked if the rest of the flags are the same as before?

plugin.go Outdated
@@ -73,18 +74,22 @@ func mainfestToolPath() string {
func (p *Plugin) Exec() error {
args := []string{}

if p.Config.Username == "" {
if p.Config.Username == "" && !p.Config.Insecure {
Copy link
Contributor

Choose a reason for hiding this comment

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

Why tied to the username? First of all insecure doesn't check certificates or is working without certificates, that doesn't imply anonymous authentication.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was wrong. I have separated anonymous access from insecure access.

@c0va23 c0va23 changed the title Allow insecure registry Allow insecure and/or anonymous registry Nov 26, 2019
@c0va23
Copy link
Contributor Author

c0va23 commented Nov 26, 2019

@tboerger, I've separated insecure access from anonymous access. And tested it together on full pipeline.

Separately, I checked that the plugin will return errors if you do not specify a password or username.

Checked only under linux, to windows I have no access.

@tboerger tboerger merged commit 2b1f335 into drone-plugins:master Nov 26, 2019
@c0va23 c0va23 deleted the feature/insecure-registry branch November 26, 2019 12:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants