SchemaStore / SchemaStore/schemastore
Traefik v2 schema doesn't reflect actual let's encrypt challenge options
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 2.3k
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 124
Description
Area with issue?
JSON Schema
✔️ Expected Behavior
The TLS, DNS and HTTPS Resolver options should support boolean values. Some (HTTPS) allows further options like the entryPoint (works).
See: --certificatesresolvers.myresolver.acme.tlschallenge=true from doc.traefik.io
❌ Actual Behavior
The schema defines all three as object only.
YAML or JSON file that does not work.
certificatesResolvers:
tls_resolver:
acme:
tlsChallenge: true
IDE or code editor.
Visual Studio Code
Are you making a PR for this?
No, someone else must create the PR.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Traefik v2 JSON Schema and compare its TLS, DNS and HTTPS resolver challenge definitions with the documented boolean form and the YAML example. Update the schema so those options accept boolean values while preserving additional HTTPS options such as entryPoint, then validate the schema against the example configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, yaml
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100