Anyone know the reason for needing

pulumi.String

instead of just a Go string?

It’s a type that is compatible with all the places that require what is fundamentally a future value (i.e.

pulumi.StringInput

).

oh gotchya so its more of a placeholder

In a way, yes. I think others will chime in with a more complete explanation, but most Pulumi resources will allow you to take in a future value for parameters, and so you need a way to wrap an explicit value (i.e. a

string

) into something that adheres to that interface.