fjall 3.4.1 → 3.6.0

package/bin/assets/generators/domain/files/infrastructure.ts

@@ -6,11 +6,11 @@ import {
 // Fjall-managed domain — edit this file to add or change records.
 // See https://docs.fjall.io/resources/networking/domain for the Domain construct API.
 
-const app = App.getApp("<%= safeZoneName %>Domain");
+const app = App.getApp("<%= domainStackName %>");
 // The stack name is Fjall's domain deploy contract (getDomainStackName) —
 // the CLI records and resolves the deployed domain by this exact
 // CloudFormation stack name. Do not rename it.
-const stack = app.getStack("<%= safeZoneName %>Domain").getStack();
+const stack = app.getStack("<%= domainStackName %>").getStack();
 
 new Domain(stack, "<%= safeZoneName %>", {
   registrar: "route53",
@@ -20,6 +20,11 @@ new Domain(stack, "<%= safeZoneName %>", {
 <% } -%>
   certificates: [
     { domainName: "<%= domainName %>" },
+    // Serving this zone through CloudFront (staticsite/cdn)? Add a viewer
+    // certificate with cloudFront: true — it is minted in us-east-1 (the
+    // only region CloudFront accepts) and publishes the zone-level
+    // us-east-1 certificate export the deploy binding carries, e.g.:
+    //   { domainName: "www.<%= domainName %>", cloudFront: true },
   ],
   records: [],
 });
@@ -29,3 +34,7 @@ new Domain(stack, "<%= safeZoneName %>", {
 // and delegatedSubdomain set; the Fjall CLI injects parentDelegationRoleArn
 // (ManagedDomainBinding.delegationRoleArn) so the child UPSERTs its NS
 // records into this zone. This apex declares no delegations[].
+// Adopting an EXISTING child zone instead of creating one? Set hostedZoneId
+// and adoptedNameServers (both together) on the child Domain — the literals
+// feed the parent NS UPSERT because an imported zone exposes no name-server
+// attribute at synth.