-
Notifications
You must be signed in to change notification settings - Fork 37
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
containerregistry:Task resource fails to create with InvalidRequestBody error #736
Comments
Thank you for reporting this @guidola Could you please run the same deployment with debug options Thank you in advance and sorry for the trouble! |
I am running version |
It seems the data is there on the put requests but getting this error still
|
If you look at the spec for there are parameters for step that cannot be set in pulumi nor are populated with defaults by the provider. Might that be the issue? Seee https://docs.microsoft.com/en-us/rest/api/containerregistry/tasks/create#agentproperties |
Good point, that's likely the cause. The reason we don't generate three subtypes is that the I submitted Azure/azure-rest-api-specs#13891 |
Thanks for the prompt reaction. I assume there is no workaround to get that type of resource created until the spec is fixed upstream correct? |
Not in the short term, unfortunately. We'll likely make a fork of the specs repo to fix issues like this, but we need to understand the process and tradeoffs first. |
It turns out this is fixed in v20190601preview: https://github.com/pulumi/pulumi-azure-native/blob/master/sdk/nodejs/containerregistry/v20190601preview/task.ts#L230 We aren't picking preview versions for top-level resources by default. Maybe we should make an exception here. |
are you planning in doing a minor release of the provider any time soon to make the fix available? |
yes, I'll do it within 1-2 days |
Expected behavior
The resources would succeed in creating or, at least, prompt an error about the invalid present configuration if any.
Current behavior
The resource fails to create and a cryptic message re. not having a body or missing a discriminator is presented. Analyzing the resource properties there is no evident discriminator key so one might assume there is some internal problem inside the provider that is triggering a request with an empty body?
Steps to reproduce
Context (Environment)
Affected feature
azure-native:containterregistry/Task
The text was updated successfully, but these errors were encountered: