SchemaStore/schemastore

Traefik v2 schema doesn't reflect actual let's encrypt challenge options

Open

#3,371 opened on Nov 6, 2023

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)JavaScript (2,208 forks)github user discovery
BugHelp Wanted

Repository metrics

Stars
 (3,774 stars)
PR merge metrics
 (Avg merge 4d 11h) (141 merged PRs in 30d)

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

Research direction
Modify the JSON schema to allow boolean values for tlsChallenge, dnsChallenge, and httpChallenge in the acme section of certificatesResolvers.
Tech stack
javascript
Domain
tooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJSON Schema
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80