Skip to content
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
This repository was archived by the owner on Nov 24, 2025. It is now read-only.

deliveryservices/sslkeys/generate/letsencrypt doesn't mention deliveryservice key #4478

@ericholguin

Description

@ericholguin

I'm submitting a ...

  • bug report
  • new feature / enhancement request
  • improvement request (usability, performance, tech debt, etc.)
  • other

Traffic Control components affected ...

  • CDN in a Box
  • Documentation
  • Grove
  • Traffic Control Client
  • Traffic Monitor
  • Traffic Ops
  • Traffic Ops ORT
  • Traffic Portal
  • Traffic Router
  • Traffic Stats
  • Traffic Vault
  • unknown

Current behavior:

When making a POST request to deliveryservices/sslkeys/generate/letsencrypt you must have either key or deliveryservice, representing a delivery service xmlid.

If you have both in your request body then their values need to match. The documentation should also mention this.

The documentation does not mention the deliveryservice key, only the key key. The documentation should be updated or if the deliveryservice key should not be allowed then this should be updated accordingly.

Expected / new behavior:

Minimal reproduction of the problem with instructions:

Anything else:

https://traffic-control-cdn.readthedocs.io/en/latest/api/v2/deliveryservices_sslkeys_generate_letsencrypt.html

Metadata

Metadata

Assignees

No one assigned

    Labels

    Traffic Opsrelated to Traffic Opsbugsomething isn't working as intendeddocumentationrelated to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions