Duplicate config errors in templates #401
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
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: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 inPulumi.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.
The text was updated successfully, but these errors were encountered: