Skip to content
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

AcceptedProtocols on RoutingRuleArgs of Azure FrontDoor not accepting list #99

Open
cberon-alliant opened this issue Aug 23, 2024 · 0 comments
Labels
kind/bug Some behavior is incorrect or out of spec

Comments

@cberon-alliant
Copy link

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

        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

@cberon-alliant cberon-alliant added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Aug 23, 2024
@cleverguy25 cleverguy25 removed the needs-triage Needs attention from the triage team label Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

No branches or pull requests

2 participants