Page Comparison

Best practice to use <your company name/<your group name>:<version> for the prefs-name, since you'll probably want a unique set of default rules per group, especially for VPC subnets usage and az's.

"prefs-name": {
    "comment": "the name to associate with this set of preferences",
    "value": "nordstrom-sets:1.0"
  }

  "resource-namer": {
    "comment": ["script to run for naming resources in our vpc."],
    "value": "lib/namer.py"
  }

"stock-templates": {
   "comment": ["overrides of (and additions to) the yac stock templates for our VPC."],
   "asg":  "stack/yac-asg-stack.json",
   "db":   "stack/yac-db-stack.json",
   "eelb": "stack/yac-eelb-stack.json",
   "efs":  "stack/yac-efs-stack.json",
   "ielb": "stack/yac-ielg-stack.json"
 }

The black magic part is provided by the script referenced here.

This input scripts are one of things that make yac so flexible.

The script can be used to implement arbitrary business logic (e.g. for mapping resources to VPC subnets).

  "vpc-inputs": {
    "comment": ["script to run for getting additional parameters for resources in our VPCs that ",
                "are driven by sets resource-placement business logic."],
    "value": "lib/inputs.py"
  }

  "vpc-params": {
    "subnets-name-tags": {
      "comment": ["The substring used to identify the subnets (by name) where yac resources should",
                  "be placed in our VPCs, one substring per layer."],
      "public":  "external-public-general",
      "dmz":     "external-private-general",
      "private": "internal-general"
    }, 
    "db-subnet-group-name-substring": {
      "comment": "The db subnet group we should use should contain this substring for all vpcs",
      "value": "internalgeneral"
    },
    "ntp-servers": {
      "comment": "The ntp servers that can be polled to sync time. Must use a semicolon delimitter (per our typical boot.sh files)",
      "value": "ntp001-6a.net.nordstrom.net;ntp319-1a.net.nordstrom.net"
    },        
    "vpc-name-tags": {
      "comment": "the default vpc for each environment",
      "dev":     "continuous",
      "stage":   "staging",
      "prod":    "infrastructure",
      "archive": "infra"
    }}