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
letsencrypt.azure.core lists Microsoft.Azure.Management.WebSites as a dependency with the condition: >= 2.0.1
However upgrading Microsoft.Azure.Management.WebSites to version 3.0.0 results in:
Error during Request or install certificate System.MissingMethodException: Method not found: 'Void Microsoft.Azure.Management.WebSites.Models.Certificate..ctor(System.String, System.String, System.String, System.String, System.String, System.String, System.Collections.Generic.IDictionary`2<System.String,System.String>, System.String, System.String, System.Collections.Generic.IList`1<System.String>, Byte[], System.String, System.String, System.String, System.Nullable`1<System.DateTime>, System.Nullable`1<System.DateTime>, System.String, System.Nullable`1<Boolean>, Byte[], System.String, Microsoft.Azure.Management.WebSites.Models.HostingEnvironmentProfile, System.String, System.String, System.Nullable`1<Microsoft.Azure.Management.WebSites.Models.KeyVaultSecretStatus>, System.String)'.
at LetsEncrypt.Azure.Core.Services.WebAppCertificateService.<Install>d__3.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at LetsEncrypt.Azure.Core.Services.WebAppCertificateService.Install(ICertificateInstallModel model)
at LetsEncrypt.Azure.Core.CertificateManager.<RequestAndInstallInternalAsync>d__15.MoveNext()
Looking at the ctor, looks like 3.0.0 indeed broke backwards compatibility (added an additional canonicalName param to the ctor). So letsencrypt.azure.core should be either upgraded, or specified with the correct dependency, namely >= 2.0.1 && < 3.0.0
The text was updated successfully, but these errors were encountered:
ohadschn
changed the title
Update Microsoft.Azure.Management.WebSites or lock version
Update Microsoft.Azure.Management.WebSites or constrain dependency version
Jun 8, 2020
ohadschn
added a commit
to ohadschn/letsencrypt-webapp-renewer
that referenced
this issue
Jun 8, 2020
letsencrypt.azure.core
listsMicrosoft.Azure.Management.WebSites
as a dependency with the condition:>= 2.0.1
However upgrading
Microsoft.Azure.Management.WebSites
to version 3.0.0 results in:Looking at the ctor, looks like 3.0.0 indeed broke backwards compatibility (added an additional
canonicalName
param to the ctor). Soletsencrypt.azure.core
should be either upgraded, or specified with the correct dependency, namely>= 2.0.1 && < 3.0.0
The text was updated successfully, but these errors were encountered: