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

Field 'registries' on 'internal.Config' must be a '[]internal.Registry'; got 'string' instead #262

Closed
wSedlacek opened this issue Sep 19, 2024 · 2 comments · Fixed by #268
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@wSedlacek
Copy link

What happened?

When trying to use registries on the dockerBuild.Provider() the following error occurs

Field 'registries' on 'internal.Config' must be a '[]internal.Registry'; got 'string' instead

Example

  const provider = new dockerBuild.Provider(containerRegistry, {
    registries: [{ address: `${protocol}//${registry.host}`, username, password }],
  });

Output of pulumi about

CLI
Version 3.133.0
Go Version go1.23.1
Go Compiler gc

Plugins
KIND NAME VERSION
language nodejs 3.133.0-dev.0

Host
OS ubuntu
Version 22.04
Arch x86_64

This project is written in nodejs: executable='/home/coder/.local/state/fnm_multishells/4830_1726756733695/bin/node' version='v20.14.0'

TYPE URN
pulumi:pulumi:Stack urn:pulumi:development-1bba0bae::rocket::pulumi:pulumi:Stack::rocket-development-1bba0bae
pulumi:providers:pulumi urn:pulumi:development-1bba0bae::rocket::pulumi:providers:pulumi::default
pulumi:providers:aws urn:pulumi:development-1bba0bae::rocket::pulumi:providers:aws::default_6_52_0
pulumi:pulumi:StackReference urn:pulumi:development-1bba0bae::rocket::pulumi:pulumi:StackReference::development-1bba0bae
pulumi:providers:kubernetes urn:pulumi:development-1bba0bae::rocket::pulumi:providers:kubernetes::coder
kubernetes:helm.sh/v3:Release urn:pulumi:development-1bba0bae::rocket::kubernetes:helm.sh/v3:Release::secrets
kubernetes:helm.sh/v3:Release urn:pulumi:development-1bba0bae::rocket::kubernetes:helm.sh/v3:Release::security
kubernetes:helm.sh/v3:Release urn:pulumi:development-1bba0bae::rocket::kubernetes:helm.sh/v3:Release::pg-config
kubernetes:helm.sh/v3:Release urn:pulumi:development-1bba0bae::rocket::kubernetes:helm.sh/v3:Release::roles
kubernetes:helm.sh/v3:Release urn:pulumi:development-1bba0bae::rocket::kubernetes:helm.sh/v3:Release::pg-cluster
pulumi:providers:command urn:pulumi:development-1bba0bae::rocket::pulumi:providers:command::default_1_0_1
pulumi:providers:docker-build urn:pulumi:development-1bba0bae::rocket::pulumi:providers:docker-build::default

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@wSedlacek wSedlacek added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Sep 19, 2024
@blampe blampe added awaiting-feedback and removed needs-triage Needs attention from the triage team labels Sep 23, 2024
@blampe
Copy link
Contributor

blampe commented Sep 23, 2024

@wSedlacek what version of the docker-build provider are you using?

@wSedlacek
Copy link
Author

@blampe the plugin is also 0.0.6.
The TypeScript interface is also v0.0.6

pulumi plugin ls
NAME          KIND      VERSION  SIZE    INSTALLED   LAST USED
command       resource  1.0.1    35 MB   2 days ago  2 days ago
docker        resource  4.5.5    49 MB   2 days ago  2 days ago
docker-build  resource  0.0.6    118 MB  2 days ago  2 days ago
kubernetes    resource  4.18.1   214 MB  2 days ago  2 days ago

TOTAL plugin cache size: 416 MB

@pulumi-bot pulumi-bot added needs-triage Needs attention from the triage team and removed awaiting-feedback labels Sep 23, 2024
@blampe blampe removed the needs-triage Needs attention from the triage team label Sep 26, 2024
blampe added a commit that referenced this issue Sep 27, 2024
Fixes #262.

@iwahbe I realized while putting this together that the provider config
case wasn't actually tested e2e, and I'm skeptical it was ever actually
working. I think it would be reasonable to pull in
#253 IMO.
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants