Unable to using pulumi.Map as input to pulumi.StringMapInput

[phillipedwards]

What happened?

Unable to using pulumi.Map as input to pulumi.StringMapInput when using pulumi-random@4.11.2.

Expected Behavior

pulumi up succeeds.

Steps to reproduce

Run the following program twice; once with pulumi-random@4.8.0 and again with pulumi-random@4.11.2. The first up succeeds and the incurs a compiler warning.

package main

import (
	"github.com/pulumi/pulumi-random/sdk/v4/go/random"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {

		n := 2

		m := pulumi.Map{
			"hi": pulumi.String("hello"),
		}

		_, err := random.NewRandomId(ctx, "rand", &random.RandomIdArgs{
			ByteLength: pulumi.ToOutput(n).(pulumi.IntOutput),
			Keepers:    m,
		})

		if err != nil {
			return err
		}

		return nil
	})
}

Output of pulumi about

Dependencies:
NAME VERSION
github.com/pulumi/pulumi-random/sdk/v4 4.11.2
github.com/pulumi/pulumi/sdk/v3 3.55.0

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

[lukehoban]

This appears to have been introduced with #260, which changed the schema for Keepers from:

                "keepers": {
                    "type": "object",
                    "additionalProperties": {
                        "$ref": "pulumi.json#/Any"
                    },
                    "description": "Arbitrary map of values that, when changed, will\ntrigger a new id to be generated. See\nthe main provider documentation for more information.\n"
                },

to:

                "keepers": {
                    "type": "object",
                    "additionalProperties": {
                        "type": "string"
                    },
                    "description": "Arbitrary map of values that, when changed, will trigger recreation of resource. See the main provider documentation for more information.\n"
                },

That is - it appears to be incorrectly requiring that the values of the keepers object are strings.

[AaronFriel]

The upstream made this change in v3.4.0 provider with the same impact on their users as we saw - restricting the map to string elements - and our release being a minor version bump was in keeping with our versioning policy for breaking changes.

We're going to take a look at that policy and what we can do in the future to mitigate this for users.