https://pulumi.com logo
Title
p

prehistoric-nail-50687

12/11/2020, 12:34 PM
I just updated to
@pulumi/azure-nextgen
from
^0.2.8
to
^0.3.0
and now I get this:
azure-nextgen:web/latest:WebApp (yoo-ci-hooks):
    error: Code="NoRegisteredProviderFound" Message="No registered resource provider found for location 'switzerlandnorth' and API version '2020-09-01' for type 'sites'. The supported api-versions are '2020-06-01, 2019-08-01, 2018-11-01, 2018-02-01, 2016-08-01, 2015-08-01-preview, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01, 2014-04-01-preview, 2015-01-01, 2015-11-01, 2016-09-01, 2017-08-01, 2018-12-01-alpha'. The supported locations are 'southcentralus, msftwestus, msfteastus, msfteastasia, msftnortheurope, eastus2stage, centralusstage, southafricanorth, westus, australiaeast, brazilsouth, southeastasia, centralus, japanwest, centralindia, uksouth, canadaeast, koreacentral, francecentral, northeurope, westus2, eastus, westindia, eastus2, australiacentral, germanywestcentral, norwayeast, uaenorth, switzerlandnorth, northcentralus, ukwest, australiasoutheast, koreasouth, canadacentral, westeurope, southindia, westcentralus, eastasiastage, northcentralusstage, eastasia, japaneast'."
I have to say that I don’t quite understand the versioning behind all this, but does this say that my region
switzerlandnorth
does not support the api version required by
pulumi nextgen 0.3.0
?
t

tall-librarian-49374

12/11/2020, 1:47 PM
This means that Azure doesn’t have the latest version of this resource API in this region. Replace Latest with V20200601.
Latest
version always picks the latest stable API version, which may change from one package version to the other (which it did in 0.2.8->0.3.0)
Sometimes, Microsoft publishes new versions before they are available everywhere
p

prehistoric-nail-50687

12/11/2020, 1:55 PM
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.
t

tall-librarian-49374

12/11/2020, 1:58 PM
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.
And we ship them in every release, including minor updates
p

prehistoric-nail-50687

12/11/2020, 2:00 PM
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
t

tall-librarian-49374

12/11/2020, 2:01 PM
You can see this - super manually - by looking at namespaces and modules
THere’s a new namespace V20200901 under web
Which means it’s the latest now
p

prehistoric-nail-50687

12/11/2020, 2:02 PM
ok, thanks
t

tall-librarian-49374

12/11/2020, 2:03 PM
The not-yet-written guide will suggest pinning versions for long-lived infrastructure instead of using latest
p

prehistoric-nail-50687

12/11/2020, 2:05 PM
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.
t

tall-librarian-49374

12/11/2020, 2:07 PM
t

tall-needle-56640

12/11/2020, 9:11 PM
@prehistoric-nail-50687 Do you think something like this would help?
p

prehistoric-nail-50687

12/13/2020, 9:56 AM
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?
t

tall-librarian-49374

12/13/2020, 11:04 AM
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.
👍 1