Provider-namespace configuration values should not have a type

[scottslowe]

What happened?

Architecture templates that leverage provider-namespace configuration values (like aws:region or gcp:project) are broken following the implementation of hierarchical configuration (as implemented via pulumi/pulumi#10832). This appears to be due to the fact that the architecture templates included a type field for provider-namespace configuration values, and that field is no longer supported/allowed.

Steps to reproduce

1. Run pulumi new kubernetes-gcp-yaml.
2. Observe the error that results:

error: template 'kubernetes-gcp-yaml' is currently broken: could not unmarshal '/Users/slowe/.pulumi/templates/kubernetes-gcp-yaml/Pulumi.yaml': Configuration key 'gcp:project' is not namespaced by the project and should not define a type

Expected Behavior

It's expected that pulumi new will work and create a new project as expected.

Actual Behavior

The pulumi new command fails with an error, and there is no obvious workaround for users.

Output of pulumi about

CLI
Version      3.49.0
Go Version   go1.19.4
Go Compiler  gc

Host
OS       darwin
Version  12.6.1
Arch     arm64

Backend
Name           pulumi.com
URL            https://app.pulumi.com/scottslowe
User           scottslowe
Organizations  scottslowe

Pulumi locates its logs in /var/folders/c_/1pdwtg4j5zx4dvx5t6qp9v180000gn/T/ by default

Additional context

Confirmed on two different macOS systems, one running Pulumi 3.49.0 (that's the output of pulumi about shown above) and another system running Pulumi 3.45.0.

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).

[scottslowe]

#478 will fix the problem and close the issue, currently awaiting review and tests to complete

[scottslowe]

Just waiting on tests to finish on #478 before merging (which will complete/fix/close this).