Add MonPetitBistro.com template

[EstebX]

Description

Add a new Domain Connect template for monpetitbistro.com to automate DNS configuration for custom domains.

MonPetitBistro is a website creation platform. Users connect their custom domains to their websites by configuring DNS records to point to our Cloudflare server (for example, edge.monpetitbistro.com). This template enables the synchronous Domain Connect flow, allowing users of compatible DNS providers to automatically configure their domain with a single click, including routing and SSL validation via delegated DCV.

Type of change

Please mark options that are relevant.

• New template
• Bug fix (non-breaking change which fixes an issue in the template)
• New feature (non-breaking change which adds functionality to the template)
• Breaking change (fix or feature that would cause existing template behavior to be not backward compatible)

How Has This Been Tested?

Please mark the following checks done

• Template functionality checked using Online Editor
• Template file name follows the pattern <providerId>.<serviceId>.json
• resource URL provided with logoUrl is actually served by a webserver

Checklist of common problems

Mark all the checkboxes after conducting the check. Comment on any point which is not fulfilled.
See Template Quality Guidelines for details and rationale on each rule.

• syncPubKeyDomain is set — this is mandatory; omitting it requires explicit justification in the PR description or the PR will be rejected
• warnPhishing is not set alongside syncPubKeyDomain — the two must not appear together
• syncRedirectDomain is set whenever the template uses redirect_uri in the synchronous flow
• no TXT record contains SPF content ("v=spf1 ...") — use the SPFM record type instead
• txtConflictMatchingMode is set on every TXT record that must be unique per label or content prefix (e.g. DMARC)
• no variable is used as a bare full record value (e.g. @ TXT "%foo%") unless necessary — prefer @ TXT "service-foo=%foo%"; if bare, justify in the PR description
• no variable is used in the host field to create a subdomain — use the host parameter or multiInstance instead
• %host% does not appear explicitly in any host attribute
• essential is set to OnApply on records the end user may need to modify or remove without breaking the template (e.g. DMARC)

Online Editor test results

Editor test link(s):

• Test Nb. 1
• Test Nb. 2

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

Linter OK

monpetitbistro.com.website.json

Level	Code	Note
info	DCTL1038	APEXCNAME and REDIRxxx records are not widely supported

[EstebX]

I think my version is fine overall, and the problem is with the linter.

I found the same issue on this template, which is similar to mine.
https://github.com/Domain-Connect/Templates/blob/master/realgeeks.com.website_and_crm.json

[EstebX]

@pawel-kow

I was referring to a different PR because I was discussing it with the person who created it; it was in that PR that I mentioned the APEXCNAME name needed for manual merging. Please excuse the confusion.

[pawel-kow]

@pawel-kow

I was referring to a different PR because I was discussing it with the person who created it; it was in that PR that I mentioned the APEXCNAME name needed for manual merging. Please excuse the confusion.

FWIW APEXCNAME is now supported in the editor:
Example

If you like Domain Connect consider supporting the project:
Buy me a coffee ☕️

[github-actions]

PR Description Check Passed

All required sections are filled in correctly.

Details

  OK  Type of change: 1/4 checkboxes ticked
  OK  How Has This Been Tested?: all 3 checkboxes ticked
  OK  Checklist of common problems: 9/9 checkboxes ticked
  OK  Online Editor test results: 2 link(s) found
  OK  Template coverage: all 1 template(s) covered
Labels to remove: Checklist of common problems not complete, Forged editor links, PR description incomplete, Test links missing

PR description check PASSED

[EstebX]

@pawel-kow
I was referring to a different PR because I was discussing it with the person who created it; it was in that PR that I mentioned the APEXCNAME name needed for manual merging. Please excuse the confusion.

FWIW APEXCNAME is now supported in the editor: Example

If you like Domain Connect consider supporting the project: Buy me a coffee ☕️

Thanks works now!