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
Structured configuration errors in Pulumi.yaml (which work in Pulumi.stack.yaml) #16056
Comments
config in Pulumi.yaml is called project level configuration, and doc at concepts/config - Project Level Configuration I also been confused by the difference schema of project level & stack level configuration. hope the doc can be more clear~~ |
stack config is just values, project config is values and types/schema. That necessitates some changes in how they're written.
We did consider making this syntax consistent and requiring it for simple values like strings/numbers as well but err'd on keeping simple values simple. We need this nesting under a "value" key for objects though so we can tell the difference between "here's just an object value" and "here's an object describing a schema".
I think that error's fairly clear? You need to set "items" to tell the system what the type of items in the array is. |
What happened?
When attempting to create a default config in Pulumi.yaml as follows:
we receive the following error:
This same configuration declaration works fine in Pulumi.{stack}.yaml.
There is a workaround with an odd syntax:
But, typing of a key does not work either:
Resulting in the following error:
Example
see above
Output of
pulumi about
3.113.3
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).
The text was updated successfully, but these errors were encountered: