Add storefront custom domain configuration for Shopi.lk

[ruzny-ramzan]

Description

Adds a new Domain Connect template for Shopi.lk Storefront service.

This template enables automatic DNS configuration for connecting a customer domain to a Shopi storefront. The template only provisions routing DNS records required for SaaS onboarding. SSL validation and certificate provisioning are handled separately by Shopi via Cloudflare for SaaS using HTTP ownership validation.

This template is intentionally limited to routing configuration and does not include TXT verification or SSL validation records.

---

Type of change

• 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?

• Schema validated using JSON Schema [template.schema](./template.schema)
• Template functionality checked using Online Editor
• Template is checked using template linter
• Template file name follows the pattern <providerId>.<serviceId>.json
• Resource URL provided with logoUrl is served by a webserver

---

Checklist of common problems

• Digital signatures are used and syncPubKeyDomain specified
• syncRedirectDomain is specified for synchronous redirect flow
• No TXT record with SPF content included
• No TXT record conflict matching issues
• Variables limited to smallest scope
• No variables used as host names
• No explicit usage of %host% in host attribute
• essential setting used appropriately

---

Template Behavior Notes

This template provisions:

• CNAME record for storefront routing

It intentionally does NOT provision:

• SSL validation TXT records
• Cloudflare SaaS ownership verification records
• Certificate provisioning records

These are handled dynamically by Shopi backend services after DNS routing is established.

---

Example variable values

"testData": {
  "testingSet": {
    "variables": {
      "domain": "example.com",
      "host": "shop"
    },
    "results": [
      {
        "type": "CNAME",
        "name": "shop",
        "ttl": 3600,
        "data": "api.shopi.lk"
      }
    ]
  }
}

[github-actions]

Linter OK:

[kerolasa]

The template file should not use separate directory. Please move it in correct place, using expected name:

mv ./shopi.lk/storefront.json ./shopi.lk.storefront.json

Secondly, the linter failed to detect issue because the template was in unexpected directory. I took liberty to have check the template manually, and got the following error. Please fix this one as well.

$ dc-template-linter shopi.lk.storefront.json 
2026-02-11T10:44:29Z ERR code=DCTL1012 dctl_note="record host must not be @ when template hostRequired is false" groupid= record=0 template=shopi.lk.storefront.json type=CNAME

https://github.com/Domain-Connect/dc-template-linter/wiki/DCTL1012

[pawel-kow]

Also very confusing is the PR description, which looks legit, but contains statements like "syncRedirectDomain is specified for synchronous redirect flow" which do not match the template not containing syncRedirectDomain at all.
AI hallucinating again?

[pawel-kow]

file naming/location and other issues

[pawel-kow]

why starting with two?

[ruzny-ramzan]

You nailed it. I thought version 2 get higher priority that's why I set it to 2. If I want to set it back to 1, then no issues. I'll do it.