You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears on the latest release, GetConfigPart now requires ContentType to be set despite being documented to defaulting to text/plain. Upon looking at the upstream provider, it also appears to be optional and default to text/plain.
Example
N/A
Output of pulumi about
N/A
Additional context
This looks to have changed here as part of the latest release.
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:
What happened?
It appears on the latest release, GetConfigPart now requires
ContentType
to be set despite being documented to defaulting totext/plain
. Upon looking at the upstream provider, it also appears to be optional and default totext/plain
.Example
N/A
Output of
pulumi about
N/A
Additional context
This looks to have changed here as part of the latest release.
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: