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
When creating a new Azure FrontDoor, the code in the docs and AI does not work. There's no way to pass a list of protocols (http/https) into the object. This is a blocking issue for having a functional FrontDoor instance.
Example
var frontDoor = new FrontDoor("frontDoor", new FrontDoorArgs
{
ResourceGroupName = resourceGroup.Name,
FrontDoorName = "myFrontDoor",
RoutingRules =
{
new RoutingRuleArgs
{
Name = "redirectToAppService",
AcceptedProtocols = { FrontDoorProtocol.Http, FrontDoorProtocol.Https },
CS1950 The best overloaded Add method 'InputList<Union<string, FrontDoorProtocol>>.Add(params Input<Union<string, FrontDoorProtocol>>[])' for the collection initializer has some invalid arguments
Output of pulumi about
CLI
Version 3.129.0
Go Version go1.22.6
Go Compiler gc
Host
OS Microsoft Windows 10 Enterprise
Version 10.0.19045 Build 19045
Arch x86_64
Backend
Name pulumi.com
URL https://app.pulumi.com
User Unknown
Organizations
Token type personal
Additional context
No response
Contributing
No response
The text was updated successfully, but these errors were encountered:
What happened?
When creating a new Azure FrontDoor, the code in the docs and AI does not work. There's no way to pass a list of protocols (http/https) into the object. This is a blocking issue for having a functional FrontDoor instance.
Example
CS1950 The best overloaded Add method 'InputList<Union<string, FrontDoorProtocol>>.Add(params Input<Union<string, FrontDoorProtocol>>[])' for the collection initializer has some invalid arguments
Output of
pulumi about
CLI
Version 3.129.0
Go Version go1.22.6
Go Compiler gc
Host
OS Microsoft Windows 10 Enterprise
Version 10.0.19045 Build 19045
Arch x86_64
Backend
Name pulumi.com
URL https://app.pulumi.com
User Unknown
Organizations
Token type personal
Additional context
No response
Contributing
No response
The text was updated successfully, but these errors were encountered: