Skip to content
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

GetConfigPart input now requires ContentType to be set, where it was optional before #239

Closed
zbuchheit opened this issue Feb 22, 2024 · 0 comments · Fixed by #240
Closed
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@zbuchheit
Copy link

What happened?

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

@zbuchheit zbuchheit added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Feb 22, 2024
@iwahbe iwahbe removed the needs-triage Needs attention from the triage team label Feb 22, 2024
@iwahbe iwahbe self-assigned this Feb 22, 2024
iwahbe added a commit that referenced this issue Feb 22, 2024
Fixes #239 

This PR also enables the linter for `pulumi-cloudinit`.
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants