[CDN/CustomDomain] allow to define customHTTPS parameters during creation

[secustor]

Currently a separate API endpoint has to be called to enable CustomHTTPS with custom domains.

This is not ideal as this prevents IaC tooling such as ARM templates, Pulumi and Terraform from using this feature.

I suggest to extend the request body of put to accommodate these properties:

before:

{
  "properties": {
    "hostName": "www.someDomain.net"
  }
}

after:

{
  "properties": {
    "hostName": "www.someDomain.net",
    "customHttpsProvisioning": {
       "certificateSource": "cdn"
       ...
     }
  }
}

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cdnfdsuppgithub.

Issue Details

---

Currently a separate API endpoint has to be called enable CustomHTTPS on custom domains.

This is not ideal as this prevent IaC tooling such ARM templates, Pulumi and Terraform from using this feature.

I suggest to extend the request body of put to accommodate this properties:

before:

{
  "properties": {
    "hostName": "www.someDomain.net"
  }
}

after:

{
  "properties": {
    "hostName": "www.someDomain.net",
    "customHttpsProvisioning": {
       "certificateSource": "cdn"
       ...
     }
  }
}

Author:	secustor
Assignees:	-
Labels:	question, Network - CDN, Service Attention, customer-reported, needs-triage
Milestone:	-

[catalystasoftware]

This is also blocking us :(