pulumi / pulumi-azure-native

Azure Native Provider
Apache License 2.0
127 stars 34 forks source link

Frontdoor (Classic) endpoint missing customHttpsConfiguration option #576

Open XBeg9 opened 4 years ago

XBeg9 commented 4 years ago

I can't find customHttpsConfiguration option for TS SDK, which exists in v2020-01-01 (Frontdoors).

https://stackoverflow.com/questions/58180861/enable-https-on-azure-front-door-custom-domain-with-arm-template-deployment

mikhailshilkov commented 4 years ago

The current open API spec marks this property as read-only (it's returned from HTTP responses but can't be set in a request). Enabling HTTPs would require a POST which isn't currently mapped to our resource model.

XBeg9 commented 4 years ago

thanks @mikhailshilkov

viveklak commented 3 years ago

Reopening this to keep visibility for missing APIs. @mikhailshilkov let me know if you disagree.

flytzen commented 3 years ago

For my understanding, is it because a POST has to be made after FrontDoor is set up as per https://docs.microsoft.com/en-us/rest/api/frontdoorservice/frontdoor/frontend-endpoints/enable-https?

So, could I write a Component myself that creates FrontDoor and then does the POST? / @mikhailshilkov @dfibuch

mikhailshilkov commented 3 years ago

For my understanding, is it because a POST has to be made after FrontDoor is set up as per https://docs.microsoft.com/en-us/rest/api/frontdoorservice/frontdoor/frontend-endpoints/enable-https?

Yes, exactly.

So, could I write a Component myself that creates FrontDoor and then does the POST?

You could. Components don't have the same lifecycle as custom resources (hooks for CRUD operations), so you may have to call that POST endpoint on every pulumi run. A dynamic provider or a custom resource in the azure-native provider could be more robust option.

SlyckLizzie commented 3 years ago

Are there plans to implement this at all? I am running into the same issue. It's no longer available

mikhailshilkov commented 3 years ago

There are two possibilities:

  1. Microsoft adds a possibility to set HTTPs as part of front door API directly
  2. We need to create a custom resource that works with POST endpoints

I can't provide any insights about (1). (2) isn't currently planned because it's a non-trivial change and the issue hasn't been upvoted much yet.