Skip to content

config-map failing with "Expected string, but was null" in v4.2 #911

@mikocot

Description

@mikocot

What happened?

Pipeline failures after release of v4.2.

Pipeline code:

 uses: pulumi/actions@v4
[...]
 config-map: | # provide required configuration
   { prNumber: { value: ${{ github.event.pull_request.number }} } }

Error message
Validation failed: { "prNumber": { "value": "Expected string, but was null" } }. Object should match { [_: string]: { value: string; secret?: boolean; } }

The same happens if ${{ github.event.pull_request.number }} is provided, but it's a number, the error is then:

"Expected string, but was number"

Expected Behavior

No breaking changes in minor release.
Changes in interface communicated in release notes and PR descriptions

Steps to reproduce

See code above

Output of pulumi about

not essentiral here

Additional context

The issue can be fixed by wrapping params in double quotes or ensuring it's a string.

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

Metadata

Metadata

Assignees

Labels

area/cicdimpact/regressionSomething that used to work, but is now brokenkind/bugSome behavior is incorrect or out of specp1A bug severe enough to be the next item assigned to an engineerresolution/fixedThis issue was fixed

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions