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

Duplicate config errors in templates #401

Closed
joeduffy opened this issue Nov 5, 2022 · 0 comments · Fixed by #402
Closed

Duplicate config errors in templates #401

joeduffy opened this issue Nov 5, 2022 · 0 comments · Fixed by #402
Assignees
Labels
area/config kind/bug Some behavior is incorrect or out of spec p0 Bugs severe enough to interrupt existing work resolution/fixed This issue was fixed
Milestone

Comments

@joeduffy
Copy link
Member

joeduffy commented Nov 5, 2022

I noticed a few templates issue errors about duplicate configuration.

For example, take a fresh $ pulumi new kubernetes-gcp-yaml -y. It works fine on 3.45.0; however, after an upgrade, I see:

  pulumi:pulumi:Stack (gkek8s-dev):
    error: an unhandled error occurred: 1 error occurred:
    	*
    -error: <nil>: found duplicate config gcp:project;
    -error: <nil>: found duplicate config gcp:region;

Is that because the template itself defines the configuration keys, as well as the dev file? Isn't that how default config works, though? The project-wide YAML file can define configuration keys/values, and individual stacks can override them?

Deleting those two configuration keys from the Pulumi.yaml file and leaving them as-is in Pulumi.dev.yaml fixes the issue.

I assume this could be a bug that belongs in pulumi/pulumi, but figured I'd start by filing here since it is affecting templates.

@joeduffy joeduffy added the needs-triage Needs attention from the triage team label Nov 5, 2022
@AaronFriel AaronFriel transferred this issue from pulumi/templates Nov 7, 2022
@AaronFriel AaronFriel added kind/bug Some behavior is incorrect or out of spec p0 Bugs severe enough to interrupt existing work area/config and removed needs-triage Needs attention from the triage team labels Nov 7, 2022
@AaronFriel AaronFriel added this to the 0.80 milestone Nov 7, 2022
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/config kind/bug Some behavior is incorrect or out of spec p0 Bugs severe enough to interrupt existing work resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants