Custom Domain in production deployment

[peterpersiel]

Best practice for production deployment ist to use a custom domain.

Please check the example for prod.mtaext

abap-saas-reference-solution/extensions/examples/prod.mtaext

Line 6 in a71c5b4

app-domain: ${default-domain}

Instead of default-domain please provide example for custom domain: mydomain.com

abap-saas-reference-solution/extensions/examples/prod.mtaext

Line 7 in a71c5b4

route-prefix: -${appname}

The route-prefix should be "", so that

cis${route-prefix}.${app-domain} becomes cis.mydomain.com

and

*${route-prefix}.${app-domain} becomes *.mydomain.com

Please add wildcard route in approuter module in the prod.mtaext example so that it is clear that routes do not have to be created per subscription:

modules:
  - name: approuter
    parameters:
      routes:
        - route: "cis${route-prefix}.${app-domain}"
        - route: "*${route-prefix}.${app-domain}"

[peterpersiel]

Hi colleagues,

any updates on this?
We should have an example for prod.mtaext that we can link. Currently the values are wrong.

Regards,
Peter