rename dc design files

Author: petercrocker

CLAUDE.md

@@ -56,7 +56,7 @@ uv run infrahubctl object load objects/events/ --branch main
 uv run infrahubctl branch create <branch-name>
 
 # Load data to specific branch
-uv run infrahubctl object load objects/dc-2 --branch <branch-name>
+uv run infrahubctl object load objects/dc-cisco-s --branch <branch-name>
 ```
 
 ### Testing and Validation
@@ -275,19 +275,19 @@ uv run infrahubctl object load objects/events/
 ### Data Center Demo
 ```bash
 # Automated approach
-./scripts/demo.sh design dc-2
+./scripts/demo.sh design dc-cisco-s
 
 # Manual approach
 uv run infrahubctl branch create my-branch
-uv run infrahubctl object load objects/dc-2 --branch my-branch
+uv run infrahubctl object load objects/dc-cisco-s --branch my-branch
 # Then run generator via InfraHub UI: Actions → Generator Definitions → create_dc
 ```
 
 ## Project Structure Details
 
 - `checks/` - Validation checks for spine, leaf, edge, loadbalancer devices
 - `objects/bootstrap/` - Initial data (locations, platforms, roles)
-- `objects/dc-2/`, `dc-3.yml`, etc. - Demo scenario data
+- `objects/dc-cisco-s.yml`, `dc-arista-s.yml`, `dc-sonic-border-leafs.yml`, `dc-juniper-s.yml`, etc. - Demo scenario data
 - `objects/security/` - Security-related demo data
 - `objects/cloud_security/` - Cloud security examples
 - `objects/events/` - Event action definitions

docs/docs/concepts.mdx

@@ -28,7 +28,7 @@ Design-driven automation flips this model. Instead of defining devices, you defi
 4. Scaling means adjusting design parameters, not editing configs
 5. Architectural changes propagate automatically
 
-The demo implements this pattern. When you load `objects/dc-2.yml`, you're not defining 20 devices. You're defining a **design specification** that a generator transforms into complete infrastructure.
+The demo implements this pattern. When you load `objects/dc-cisco-s.yml`, you're not defining 20 devices. You're defining a **design specification** that a generator transforms into complete infrastructure.
 
 ### Benefits
 

docs/docs/developer-guide.mdx

@@ -38,8 +38,10 @@ infrahub-demo/
 │   ├── bootstrap/            # Initial data (locations, platforms, roles)
 │   ├── security/             # Security zones, policies, rules
 │   ├── cloud_security/       # Cloud security examples
-│   ├── dc-2.yml              # DC-2 design data
-│   └── dc-3.yml              # DC-3 design data
+│   ├── dc-cisco-s.yml            # DC-2 design data (Cisco)
+│   ├── dc-arista-s.yml           # DC-3 design data (Arista)
+│   ├── dc-sonic-border-leafs.yml # DC-4 design data (SONiC with border leafs)
+│   └── dc-juniper-s.yml          # DC-5 design data (Juniper)
 ├── generators/               # Topology generators
 │   ├── generate_dc.py        # Data center generator
 │   ├── generate_pop.py       # POP generator

docs/docs/user-walkthrough.mdx

@@ -76,7 +76,7 @@ The DC-2 design is a pre-configured data center topology specification that defi
 Load the design data onto your branch:
 
 ```bash
-uv run infrahubctl object load objects/dc-2.yml --branch add-dc2
+uv run infrahubctl object load objects/dc-cisco-s.yml --branch add-dc2
 ```
 
 Watch the output for success messages. You should see confirmations that the topology data has been loaded.
@@ -279,7 +279,7 @@ Congratulations! You've completed the full workflow:
 Now that you understand the basic workflow, you can:
 
 - **Explore variations** - Try creating DC-3 or a POP topology
-- **Modify designs** - Edit the objects/dc-2.yml file to change the topology
+- **Modify designs** - Edit the objects/dc-cisco-s.yml file to change the topology
 - **Add network services** - Create Layer 2 or Layer 3 services on top of the fabric
 - **Customize configurations** - Modify templates in the `templates/` directory
 - **Add validation checks** - Create custom checks in the `checks/` directory
@@ -324,7 +324,7 @@ You can also perform this entire workflow from the command line. Here's the abbr
 uv run infrahubctl branch create add-dc2
 
 # Load design (this automatically triggers the generator)
-uv run infrahubctl object load objects/dc-2.yml --branch add-dc2
+uv run infrahubctl object load objects/dc-cisco-s.yml --branch add-dc2
 
 # Monitor generator progress in the web interface (System → Tasks)
 # Create proposed change (easier via web interface)

objects/dc-3.yml objects/dc-arista-s.ymlobjects/dc-3.yml renamed to objects/dc-arista-s.yml

@@ -175,7 +175,7 @@ def test_07_load_dc2_design(
         logging.info("Starting test: test_07_load_dc2_design")
 
         load_dc2 = self.execute_command(
-            f"infrahubctl object load objects/dc-2.yml --branch {default_branch}",
+            f"infrahubctl object load objects/dc-cisco-s.yml --branch {default_branch}",
             address=client_main.config.address,
         )