Docs omit Servers property

[bradygaster]

I followed the docs - which are MUCH-improved and getting exciting - and ran into one issue. When I follow the tutorial explicitly the OpenApiConfigurationOptions class I created lacks the Servers property, so I get a compilation error.

I can add this manually, but I think this approach to hard-coding it is sub-optimal and I'd prefer us not recommend someone hard-code localhost into their C# code.

public List<OpenApiServer> Servers 
{ 
    get
    {
      return ( new OpenApiServer[] { new OpenApiServer { Url = "https://localhost:7071" }}).ToList();
    }
    set => throw new NotImplementedException(); 
}

Is there a way that the Functions runtime can provide this? Something we could do to mitigate the customer's need to have to do this OR provide some sort of guidance that wouldn't require hard-coding?

[justinyoo]

Oh, the localhost one should be automatically added, without having to explicitly implement the interface. I thought it would do it. Let me check.

[bradygaster]

BTW I was able to resolve this both locally in development and post-production without making any code tweaks. Just making sure folks see that this is possible.

public List<OpenApiServer> Servers 
    { 
      get
      {
        return ( new OpenApiServer[] { new OpenApiServer { Url = 
          //"https://localhost:7071"
          Environment.GetEnvironmentVariable("WEBSITE_HOSTNAME")
        }}).ToList();
      }
      set => throw new NotImplementedException(); 
    }

Curious what folks would prefer?

1. We just do this in something like a DefaultOpenApiConfigurationOptions implementation of IOpenApiConfigurationOptions and ship it in the binding.
2. We don't add a DefaultOpenApiConfigurationOptions of IOpenApiConfigurationOptions, force folks to implement it, and add this approach to the tutorial and/or the template [that may or may not exist or be planned]. :)

[justinyoo]

I prefer the option 1.

[justinyoo]

This has been released to NuGet.