This message was deleted.

This means that Azure doesn’t have the latest version of this resource API in this region. Replace Latest with V20200601.

thanks @tall-librarian-49374 - as pointed out in a different thread, would be good to have some documentation about this and also to record when such a change occurs. This will allow us to monitor a single place to check if something new is available or must be present.

Yes, we owe you the docs about versioning.

also to record when such a change occurs

Where and how would you want to see that? Changes like this happen ~daily across all Azure API.

What I mean, is: I would like to see that the latest changed to a new azure API version and/or that a new API version is now supported by Pulumi. Then I guess there is some way for me to check if my location already supports this version (might be a manual check) I have do myself

You can see this - super manually - by looking at namespaces and modules

ok, thanks

The not-yet-written guide will suggest pinning versions for long-lived infrastructure instead of using latest

that sounds good - I just noticed that it is still hard to figure out which of the versions is the latest (might be a problem of my editor). I know its more less a date string, but comparing by eye is not always easy.

@prehistoric-nail-50687 Do you think something like this would help?

I understand the reasoning behind this, but it somehow feels wrong to polluts the source with version definitions all over. Also I don’t know if it is a good thing to switch between different versions the same program, e.g. is it always fine to create a resource A with version 1 and have depending resource B created with version 2? Could this potentially create some problems?

is it always fine to create a resource A with version 1 and have depending resource B created with version 2?

Yes. You kind of have to do that all the time: every resource has its own set of versions, so there isn’t one API version to fit all resources. Besides, no matter which API version you use for a given type - it’s going to be the same resource in Azure in the end.