Azure / Azure/azure-rest-api-specs

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

Open
#17,498 2 comments 10 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

customer-reported Network - CDN question Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
6k
Avg merge
2d 21h
Merged PRs (30d)
432

Description

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"
       ...
     }
  }
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked CustomHTTPS enable-custom-https REST endpoint and the current custom-domain request schema in the Azure API specifications. Trace how the request body is defined and generated, then verify that customHttpsProvisioning is accepted during creation and that the resulting specification remains valid.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, openapi
Domain
api, cloud
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.