@dns / @domain pragma

Is your feature request related to a problem? Please describe. Currently, Arc 6 is missing support for the @dns pragma; this is in part due to the fact that HTTP infra underwent some changes during the 6 buildout, in addition to adding @cdn pragma.

@dns (or alternately @domain) should come back to Architect, enabling users to define a domain they’d like to use for their app, and have it easily set up on their behalf.

Describe the solution you’d like Users should be able to define @dns (or alternately / preferably (imo) @domain), which would enable them to define a domain, and wire that domain into their existing stack.

Considerations include origins (@http vs @cdn), origin paths, and cert provisioning (and region consideration for cert provisioning for CDN support), among other things.

Describe alternatives you’ve considered This can be done manually today if one knows what to do (and how to do it). It’s not a great alternative.

[brianleroux]

Note to self: publish domains prototype macro here asap!

[brianleroux]

put some thought into the ideal declarative config

@app
foo

@domains
staging
  http qa.foo.com
  static static-qa.foo.com
  ws ws-qa.foo.com

production
  http foo.com
  static static.foo.com
  ws ws.foo.com
  
@http
post /graphql

@static
fingerprint true
spa false

@cdn
@ws