diff --git a/docs/callnote-09152025-implementation.md b/docs/callnote-09152025-implementation.md new file mode 100644 index 0000000..23ab980 --- /dev/null +++ b/docs/callnote-09152025-implementation.md @@ -0,0 +1,690 @@ +# Call Notes Implementation Plan - September 15, 2025 + +## Executive Summary +Based on the discussion between David John Arnold Jr. and Matthew Creal Morgan, this document provides a detailed technical implementation plan for improving the terraform-eks-deployment module. The primary goals are to simplify the user interface, consolidate naming conventions, and establish a robust workflow for managing multiple EKS clusters. + +## Key Insights from Call Notes + +### Core Issues Identified +1. **Interface Complexity**: Current variable structure is too complex for end users +2. **Duplicate Variables**: Repository name and cluster name should be unified +3. **Static Values Exposed**: Values that should have sensible defaults are being exposed to users +4. **Workspace Management**: Need for a centralized approach to manage multiple clusters without conflicts + +### Technical Requirements +- Use `config_json` structure as the model for the interface +- Implement single source of truth for naming +- Hide implementation details from users +- Create shared workspace for multiple cluster management + +## Detailed Implementation Plan + +### Phase 1: Module Interface Cleanup (Priority: High) + +#### 1.1 Variable Consolidation + +**Current State Analysis:** +- `name` variable controls repository name +- `cluster_config.cluster_name` controls cluster name (REMOVED) +- Multiple redundant variables exposed to users + +**Implementation Steps:** + +##### Step 1.1.1: Remove Redundant Variables +**File:** `variables.tf` +**Changes Required:** +```hcl +# REMOVE these variables or make them internal +variable "repository_template" { + # Move to locals with default value +} + +variable "repository_template_owner" { + # Move to locals with default value +} + +# REMOVE from cluster_config object +variable "cluster_config" { + type = object({ + # Remove aws_profile - build dynamically + # Remove enable_all_modules - default to true + # cluster_name already removed + }) +} +``` + +**Action Items:** +- [ ] Move static repository template values to `locals.tf` +- [ ] Remove `aws_profile` from cluster_config (build dynamically from account_name + account_id) +- [ ] Remove `enable_all_modules` variable (default behavior) +- [ ] Update variable descriptions to reflect simplified interface + +##### Step 1.1.2: Implement Dynamic AWS Profile Generation +**File:** `locals.tf` +**Implementation:** +```hcl +locals { + # Dynamic AWS profile generation + aws_profile = "${var.cluster_config.account_name}-${var.cluster_config.environment_abbr}" + + # Static template values (hidden from users) + repository_template = "template-eks-cluster" + repository_template_owner = "SCT-Engineering" + + # Default module enablement + enable_all_modules = true +} +``` + +**Action Items:** +- [ ] Add dynamic profile generation logic +- [ ] Update all references to use computed values +- [ ] Test profile generation with existing account configurations + +#### 1.2 Static Value Management + +**Current Issue:** Values like `eks_instance_disk_size`, `eks_ng_desired_size`, etc. are exposed to users but should be static defaults for Karpenter node group configuration. + +**Implementation Steps:** + +##### Step 1.2.1: Move Static Values to Module Defaults +**File:** `variables.tf` +**Changes:** +```hcl +variable "cluster_config" { + type = object({ + # Keep only user-configurable values + account_name = string + aws_account_id = string + environment_abbr = string + vpc_name = string + vpc_domain_name = string + cluster_mailing_list = optional(string) + # Remove static EKS sizing values + }) +} +``` + +**File:** `locals.tf` +**Add:** +```hcl +locals { + # Static EKS configuration for Karpenter bootstrap node group + eks_defaults = { + instance_disk_size = 200 + ng_desired_size = 3 + ng_max_size = 10 + ng_min_size = 3 + } +} +``` + +**Action Items:** +- [ ] Move all static EKS sizing values to locals +- [ ] Update cluster.hcl template to use local values +- [ ] Document why these values are static (Karpenter will manage actual workload nodes) +- [ ] Validate that existing configurations still work + +#### 1.3 Config JSON Interface Model + +**Goal:** Simplify the user interface to match the minimal `config_json` structure shown in the call. + +**Target Interface Structure:** +```json +{ + "environment": "dev", + "region": "us-gov-east-1", + "account": { + "account_name": "csvd-dev-ew", + "aws_account_id": "229685449397", + "environment_abbr": "dev" + }, + "vpc": { + "vpc_name": "vpc3-csvd-dev", + "vpc_domain_name": "dev.inf.csp1.census.gov" + }, + "cluster": { + "cluster_mailing_list": "david.j.arnold.jr@census.gov" + } +} +``` + +**Implementation Steps:** + +##### Step 1.3.1: Create Simplified Variable Structure +**File:** `variables.tf` +**New Structure:** +```hcl +variable "name" { + description = "The name used for both repository and cluster" + type = string +} + +variable "environment" { + description = "Environment name (e.g., dev, prod)" + type = string +} + +variable "region" { + description = "AWS region" + type = string +} + +variable "account_config" { + description = "AWS account configuration" + type = object({ + account_name = string + aws_account_id = string + environment_abbr = string + }) +} + +variable "vpc_config" { + description = "VPC configuration" + type = object({ + vpc_name = string + vpc_domain_name = string + }) +} + +variable "cluster_config" { + description = "Cluster-specific configuration" + type = object({ + cluster_mailing_list = optional(string) + tags = optional(map(string), {}) + }) + default = {} +} +``` + +**Action Items:** +- [ ] Restructure variables to match config_json model +- [ ] Update all template references +- [ ] Update examples to use new structure +- [ ] Create migration guide for existing users + +### Phase 2: Workspace Structure Implementation (Priority: High) + +#### 2.1 Centralized Workspace Creation + +**Current Challenge:** Users are working in separate directories causing state conflicts. + +**Solution:** Create a shared workspace that can manage multiple clusters without conflicts. + +**Implementation Steps:** + +##### Step 2.1.1: Create eks-clusters-workspace Repository +**Action Items:** +- [ ] Create new repository: `eks-clusters-workspace` (renamed from terraform-eks-workspace to better reflect that it's a workspace, not a module) +- [ ] Set up proper directory structure +- [ ] Configure remote state backend +- [ ] Set up proper permissions and team access + +**Directory Structure:** +``` +eks-clusters-workspace/ +├── main.tf # Multiple module calls +├── backend.tf # Remote state configuration +├── providers.tf # Provider configurations +├── variables.tf # Workspace-level variables +├── clusters/ +│ ├── david-cluster.tfvars # David's cluster config +│ ├── matthew-cluster.tfvars # Matthew's cluster config +│ └── prod-cluster.tfvars # Production cluster config +├── outputs.tf # Aggregate outputs +└── README.md # Usage documentation +``` + +##### Step 2.1.2: Configure Multi-Cluster Main.tf +**File:** `main.tf` +**Implementation:** +```hcl +# David's test cluster +module "david_cluster" { + source = "git::git@github.e.it.census.gov:CSVD/terraform-eks-deployment.git" + + name = "david-test-cluster" + environment = "dev" + region = "us-gov-east-1" + + account_config = { + account_name = "csvd-dev-ew" + aws_account_id = "229685449397" + environment_abbr = "dev" + } + + vpc_config = { + vpc_name = "vpc3-csvd-dev" + vpc_domain_name = "dev.inf.csp1.census.gov" + } + + cluster_config = { + cluster_mailing_list = "david.j.arnold.jr@census.gov" + tags = { + Owner = "David Arnold" + Purpose = "Testing" + } + } + + repository_teams = { + "platform-team" = "admin" + "developers" = "push" + } +} + +# Matthew's test cluster +module "matthew_cluster" { + source = "git::git@github.e.it.census.gov:CSVD/terraform-eks-deployment.git" + + name = "matthew-test-cluster" + environment = "dev" + region = "us-gov-west-1" + + # Matthew's specific configuration + account_config = { + account_name = "csvd-dev-ww" + aws_account_id = "229685449398" + environment_abbr = "dev" + } + + vpc_config = { + vpc_name = "vpc3-csvd-dev-west" + vpc_domain_name = "dev-west.inf.csp1.census.gov" + } + + cluster_config = { + cluster_mailing_list = "matthew.morgan@census.gov" + tags = { + Owner = "Matthew Morgan" + Purpose = "Testing" + } + } + + repository_teams = { + "platform-team" = "admin" + "developers" = "maintain" + } +} +``` + +**Action Items:** +- [ ] Implement multi-cluster main.tf +- [ ] Configure unique resource naming to prevent conflicts +- [ ] Set up proper state isolation per cluster +- [ ] Test parallel cluster creation + +##### Step 2.1.3: State Management Strategy +**File:** `backend.tf` +**Implementation:** +```hcl +terraform { + backend "s3" { + bucket = "csvd-terraform-state" + key = "eks-clusters-workspace/terraform.tfstate" + region = "us-gov-east-1" + dynamodb_table = "terraform-state-lock" + encrypt = true + } +} +``` + +**Action Items:** +- [ ] Configure centralized state backend +- [ ] Set up state locking mechanism +- [ ] Implement state backup strategy +- [ ] Document state management procedures + +### Phase 3: Template and Configuration Updates (Priority: Medium) + +#### 3.1 Create Module Defaults File + +**New File:** `defaults.tf` +**Implementation:** +```hcl +# defaults.tf - Default values for module configuration +# These values should not be exposed to users but are used internally by templates + +locals { + # Dynamic AWS profile generation + aws_profile = "${var.cluster_config.account_name}-${var.cluster_config.environment_abbr}" + + # Static template values (hidden from users) + repository_defaults = { + template = "template-eks-cluster" + template_owner = "SCT-Engineering" + } + + # Default module enablement + enable_all_modules = true + + # Static EKS configuration for Karpenter bootstrap node group + eks_defaults = { + instance_disk_size = 200 + ng_desired_size = 3 + ng_max_size = 10 + ng_min_size = 3 + enable_cluster_creator_admin_permissions = true + } + + # Default organization settings + organization_defaults = { + finops_project_name = "csvd_platformbaseline" + finops_project_number = "fs0000000078" + finops_project_role = "csvd_platformbaseline_app" + } +} +``` + +**Action Items:** +- [ ] Create defaults.tf file with all module defaults +- [ ] Remove hardcoded values from templates +- [ ] Update all template references to use locals +- [ ] Test template rendering with new structure + +#### 3.2 Template File Updates + +**Files to Update:** +- `templates/cluster.hcl.tf.tpl` +- `templates/README.md.tf.tpl` +- `templates/account.hcl.tf.tpl` +- `templates/region.hcl.tf.tpl` +- `templates/vpc.hcl.tf.tpl` + +**Implementation Steps:** + +##### Step 3.2.1: Update Cluster Template +**File:** `templates/cluster.hcl.tf.tpl` +**Changes Required:** +```hcl +# Use simplified variable references +cluster_name = "${cluster_name}" # Now comes from top-level name variable +aws_profile = "${aws_profile}" # Computed dynamically from locals + +# Use local defaults for EKS sizing - passed from locals, not hardcoded +eks_instance_disk_size = ${eks_instance_disk_size} +eks_ng_desired_size = ${eks_ng_desired_size} +eks_ng_max_size = ${eks_ng_max_size} +eks_ng_min_size = ${eks_ng_min_size} +enable_cluster_creator_admin_permissions = ${enable_cluster_creator_admin_permissions} + +# Organization defaults - passed from locals +finops_project_name = "${finops_project_name}" +finops_project_number = "${finops_project_number}" +finops_project_role = "${finops_project_role}" +``` + +**Action Items:** +- [ ] Update all template variable references +- [ ] Remove hardcoded values, replace with template variables +- [ ] Test template rendering with new structure +- [ ] Validate generated HCL syntax + +##### Step 3.2.2: Update Main.tf Template Calls +**File:** `main.tf` +**Implementation:** +```hcl +locals { + rendered_files = { + "root.hcl" : templatefile("${path.module}/templates/root.hcl.tf.tpl", { + environment = var.environment + }), + "environment/account.hcl" : templatefile("${path.module}/templates/account.hcl.tf.tpl", { + account_name = var.cluster_config.account_name, + aws_account_id = var.cluster_config.aws_account_id, + environment = var.environment, + environment_abbr = var.cluster_config.environment_abbr + }), + "environment/region/region.hcl" : templatefile("${path.module}/templates/region.hcl.tf.tpl", { + aws_region = var.region, + environment = var.environment + }), + "environment/region/vpc/vpc.hcl" : templatefile("${path.module}/templates/vpc.hcl.tf.tpl", { + vpc_name = var.cluster_config.vpc_name, + vpc_domain_name = var.cluster_config.vpc_domain_name, + environment = var.environment, + aws_region = var.region + }), + "environment/region/vpc/cluster/cluster.hcl" : templatefile("${path.module}/templates/cluster.hcl.tf.tpl", { + cluster_name = var.name, + cluster_mailing_list = var.cluster_config.cluster_mailing_list, + aws_profile = local.aws_profile, + eks_instance_disk_size = local.eks_defaults.instance_disk_size, + eks_ng_desired_size = local.eks_defaults.ng_desired_size, + eks_ng_max_size = local.eks_defaults.ng_max_size, + eks_ng_min_size = local.eks_defaults.ng_min_size, + enable_cluster_creator_admin_permissions = local.eks_defaults.enable_cluster_creator_admin_permissions, + finops_project_name = local.organization_defaults.finops_project_name, + finops_project_number = local.organization_defaults.finops_project_number, + finops_project_role = local.organization_defaults.finops_project_role, + tags = var.cluster_config.tags, + module_enablement_overrides = var.cluster_config.module_enablement_overrides + }), + "README.md" : templatefile("${path.module}/templates/README.md.tf.tpl", { + environment = var.environment, + cluster_name = var.name, + aws_region = var.region + }) + } +} + +module "github_repo" { + source = "git::git@github.e.it.census.gov:CSVD/terraform-github-repo.git" + + name = var.name + repo_org = var.organization + github_repo_description = "EKS Cluster Configuration for ${var.name}" + github_repo_topics = ["eks", "kubernetes", "terraform", "infrastructure"] + force_name = var.force_name + + template_repo_org = local.repository_defaults.template_owner + template_repo = local.repository_defaults.template + + github_is_private = var.is_private + github_has_issues = true + github_has_wiki = true + github_has_projects = true + + managed_extra_files = [ + for path, content in local.rendered_files : { + path = path + content = content + } + ] + archive_on_destroy = false + github_org_teams = [ + for team, permission in var.repository_teams : { + team_name = team + permission = permission + slug = lower(replace(team, " ", "-")) + id = null + bypass_rules = false + } + ] +} +``` + +**Action Items:** +- [ ] Update main.tf to pass local values to templates +- [ ] Remove repository template variables from variables.tf +- [ ] Test module with updated template calls +- [ ] Validate generated repository content + +### Phase 4: Testing and Validation (Priority: High) + +#### 4.1 Module Validation + +**Test Cases:** +1. **Single Cluster Creation** + - Deploy using simplified interface + - Verify repository creation + - Validate generated cluster configuration + - Test team permissions + +2. **Multi-Cluster Workspace** + - Deploy multiple clusters simultaneously + - Verify no resource conflicts + - Test state isolation + - Validate unique naming + +3. **Variable Migration** + - Test backward compatibility + - Validate dynamic profile generation + - Verify template rendering + +**Implementation Steps:** + +##### Step 4.1.1: Create Test Suite +**File:** `tests/module_test.go` +**Action Items:** +- [ ] Create automated test suite +- [ ] Test variable validation +- [ ] Test template rendering +- [ ] Test GitHub repository creation +- [ ] Test multi-cluster scenarios + +##### Step 4.1.2: Manual Testing Protocol +**Action Items:** +- [ ] Test with David's configuration +- [ ] Test with Matthew's configuration +- [ ] Test workspace creation and management +- [ ] Validate generated repositories +- [ ] Test cluster deployment end-to-end + +### Phase 5: Documentation and Demo Preparation (Priority: Medium) + +#### 5.1 Documentation Updates + +**Files to Create/Update:** +- `README.md` - Updated usage instructions +- `docs/MIGRATION.md` - Migration guide from old interface +- `docs/WORKSPACE_SETUP.md` - Workspace setup instructions +- `docs/TROUBLESHOOTING.md` - Common issues and solutions + +**Action Items:** +- [ ] Document new simplified interface +- [ ] Create migration guide for existing users +- [ ] Document workspace setup process +- [ ] Create troubleshooting guide + +#### 5.2 Demo Preparation + +**Demo Objectives:** +1. Show simplified user interface +2. Demonstrate multi-cluster workspace +3. Show conflict resolution +4. Demonstrate end-to-end workflow + +**Demo Script:** +1. **Introduction** (5 minutes) + - Current challenges with interface + - Goals of the improvement + +2. **Interface Simplification** (10 minutes) + - Before/after comparison + - Reduced complexity + - Hidden implementation details + +3. **Workspace Management** (10 minutes) + - Multi-cluster deployment + - State management + - Conflict avoidance + +4. **Live Demo** (15 minutes) + - Deploy test cluster + - Show generated repository + - Demonstrate team access + +**Action Items:** +- [ ] Prepare demo environment +- [ ] Create demo script +- [ ] Prepare test configurations +- [ ] Schedule dry run for September 16 + +## Implementation Timeline + +### September 15, 2025 (Today) +- [x] Complete action items analysis +- [x] Create implementation plan +- [ ] Begin Phase 1: Variable consolidation + +### September 16, 2025 +- [ ] Complete Phase 1: Module interface cleanup +- [ ] Create defaults.tf file with all module defaults +- [ ] Begin Phase 2: Workspace creation with correct naming (eks-clusters-workspace) +- [ ] Update templates to use passed variables instead of hardcoded values +- [ ] Conduct dry run demo +- [ ] Final testing and validation + +### September 17, 2025 +- [ ] Final documentation updates +- [ ] Live demonstration to team +- [ ] Gather feedback and plan next steps + +## Risk Mitigation + +### Potential Issues and Solutions + +1. **Breaking Changes** + - **Risk:** Existing users may have configurations that break + - **Mitigation:** Create migration guide and maintain backward compatibility where possible + +2. **State Conflicts** + - **Risk:** Multiple users working in same workspace + - **Mitigation:** Implement proper state locking and isolation + +3. **Variable Validation** + - **Risk:** New interface may not validate properly + - **Mitigation:** Comprehensive testing and validation suite + +4. **Repository Generation** + - **Risk:** Template changes may break repository generation + - **Mitigation:** Test all templates with new variable structure + +## Success Criteria + +1. **User Interface** + - [ ] 50% reduction in required variables + - [ ] Clear separation of user-configurable vs. internal values + - [ ] Intuitive configuration structure + +2. **Workspace Management** + - [ ] Multiple clusters can be managed without conflicts + - [ ] State isolation between cluster configurations + - [ ] Clear ownership and access patterns + +3. **Documentation** + - [ ] Complete migration guide + - [ ] Clear setup instructions + - [ ] Working examples for all scenarios + +4. **Demo Success** + - [ ] Successful live demonstration + - [ ] Positive team feedback + - [ ] Clear next steps identified + +## Next Steps After Implementation + +1. **Rollout Strategy** + - Gradual migration of existing clusters + - Training for team members + - Support for migration questions + +2. **Monitoring and Feedback** + - Track usage patterns + - Gather user feedback + - Identify areas for further improvement + +3. **Future Enhancements** + - Integration with CI/CD pipelines + - Advanced workspace management features + - Automated cluster lifecycle management + +## Contact and Responsibilities + +- **David John Arnold Jr.**: Module development, workspace setup, testing +- **Matthew Creal Morgan**: Interface design review, testing, documentation review +- **Team Demo**: September 17, 2025 + +--- + +*This implementation plan is based on the call notes from September 15, 2025, and should be updated as implementation progresses.* \ No newline at end of file diff --git a/docs/callnotes-09152025.txt b/docs/callnotes-09152025.txt new file mode 100644 index 0000000..f763c65 --- /dev/null +++ b/docs/callnotes-09152025.txt @@ -0,0 +1,1611 @@ +WEBVTT + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4249-0 +00:00:06.437 --> 00:00:07.117 +All right, cool. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4253-0 +00:00:07.117 --> 00:00:09.637 +Yeah. So we should be recording them. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4254-0 +00:00:08.377 --> 00:00:08.937 +All right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4257-0 +00:00:09.677 --> 00:00:10.557 +So yeah, all right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4259-0 +00:00:10.997 --> 00:00:11.357 +OK. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4263-0 +00:00:11.357 --> 00:00:13.037 +So a couple of things that you should +clean up. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4290-0 +00:00:14.567 --> 00:00:19.489 +This is essentially what you've defined +as your inputs that you're expecting + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4281-0 +00:00:18.297 --> 00:00:18.497 +Mm-hmm. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4290-1 +00:00:19.489 --> 00:00:21.087 +other people to fill out. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4296-0 +00:00:21.567 --> 00:00:25.687 +Compare this to what you had previously. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4303-0 +00:00:27.447 --> 00:00:29.207 +In the config JSON. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4306-0 +00:00:30.237 --> 00:00:30.517 +Right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4326-0 +00:00:31.207 --> 00:00:36.559 +Right. +So if we look at our config JSON as kind + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4326-1 +00:00:36.559 --> 00:00:41.687 +of the minimal object that we want to +handle. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4335-0 +00:00:44.157 --> 00:00:46.957 +This is the only thing that should be +modified. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4349-0 +00:00:48.487 --> 00:00:52.201 +In this scenario, +you're expecting people to go in and + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4349-1 +00:00:52.201 --> 00:00:53.687 +directly modify these. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4376-0 +00:00:56.247 --> 00:01:02.245 +Variable definitions and that probably +won't work long term like ideally we want + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4376-1 +00:01:02.245 --> 00:01:08.465 +to be able to pass and maintain an object +against the module call and that would be + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4376-2 +00:01:08.465 --> 00:01:08.687 +it. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4379-0 +00:01:08.837 --> 00:01:09.717 +Does that make sense? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4399-0 +00:01:10.827 --> 00:01:14.285 +Yeah, OK. +I mean basically what you're telling me + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4399-1 +00:01:14.285 --> 00:01:18.227 +is that the input schema from a user +doesn't make sense. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4414-0 +00:01:18.227 --> 00:01:22.429 +And config dot Jason is a better model +for me to follow as far as the interface + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4414-1 +00:01:22.429 --> 00:01:23.427 +to the module goes. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4419-0 +00:01:23.737 --> 00:01:27.137 +Yes, that's that's exactly correct now. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4417-0 +00:01:24.877 --> 00:01:25.077 +Hey. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4444-0 +00:01:30.537 --> 00:01:37.014 +Some of this is duplicative and can be +removed or referenced differently because, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4444-1 +00:01:37.014 --> 00:01:41.358 +like Buster, +Dur is just the same as cluster name like + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4444-2 +00:01:41.358 --> 00:01:43.017 +I've told you before. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4449-0 +00:01:44.557 --> 00:01:45.957 +So why are we? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4456-0 +00:01:46.517 --> 00:01:48.597 +Why are we creating it in two places? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4482-0 +00:01:48.757 --> 00:01:53.625 +We don't need AWS profile because the way +the modules handle it, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4482-1 +00:01:53.625 --> 00:01:59.317 +it builds it dynamically from the other +two account name and account ID so. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4495-0 +00:02:00.977 --> 00:02:03.177 +We don't need AWS profile at all. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4501-0 +00:02:03.177 --> 00:02:06.417 +This enable all modules true doesn't need +to be there either. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4505-0 +00:02:06.457 --> 00:02:08.577 +That's in default assumption. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4511-0 +00:02:10.377 --> 00:02:12.417 +We should probably drop slim schedule. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4520-0 +00:02:12.927 --> 00:02:17.607 +That's a different topic though, +so not a huge word worry about that. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4532-0 +00:02:19.137 --> 00:02:23.857 +This owner or whatever should be the same +as the cluster mailing list. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4545-0 +00:02:24.637 --> 00:02:27.077 +Just we're collecting an e-mail address, +right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4574-0 +00:02:27.477 --> 00:02:32.763 +And the rest of it, +like we don't even really need these here + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4542-0 +00:02:27.487 --> 00:02:27.567 +No. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4574-1 +00:02:32.763 --> 00:02:39.755 +because these are the defaults and what +they should always be the only thing that + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4574-2 +00:02:39.755 --> 00:02:43.677 +we need or collect these for is to to +inform. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4598-0 +00:02:44.977 --> 00:02:48.878 +The node group for Carpenter, +which will then create the other node + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4598-1 +00:02:48.878 --> 00:02:50.657 +groups that will run workloads. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4607-0 +00:02:51.197 --> 00:02:53.037 +OK, so that. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4605-0 +00:02:52.217 --> 00:02:53.737 +So those are relatively static. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4608-0 +00:02:54.127 --> 00:02:54.727 +Values. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4650-0 +00:02:55.377 --> 00:02:58.909 +All right, +so those static values for the eks + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4650-1 +00:02:58.909 --> 00:03:04.822 +instance, disk size, eksng, desired size, +eksng Max size and eksng min size. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4650-2 +00:03:04.822 --> 00:03:09.045 +Those should still be configurable +through the module, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4650-3 +00:03:09.045 --> 00:03:12.577 +but not necessarily presented to the user +as. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4661-0 +00:03:14.097 --> 00:03:16.337 +You you'd still want to be able to +override that though, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4665-0 +00:03:16.657 --> 00:03:17.937 +We don't have a bigger. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4666-0 +00:03:17.247 --> 00:03:19.247 +No need, they're static. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4693-0 +00:03:21.737 --> 00:03:26.100 +So again, +these values only govern the creation of + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4693-1 +00:03:26.100 --> 00:03:31.917 +the Carpenter node group, +and then the Carpenter node group creates + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4693-2 +00:03:31.917 --> 00:03:33.457 +other node groups. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4697-0 +00:03:36.537 --> 00:03:38.297 +Oh, OK, got you. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4703-0 +00:03:40.187 --> 00:03:41.347 +I I think I got you. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4714-0 +00:03:41.347 --> 00:03:45.497 +So that's configuring the Carpenter, +but then Carpenter, it manages stuff. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4718-0 +00:03:46.357 --> 00:03:46.917 +Yeah, totally. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4720-0 +00:03:46.557 --> 00:03:47.077 +Right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4721-0 +00:03:47.397 --> 00:03:48.317 +Alright, sweet. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4723-0 +00:03:51.757 --> 00:03:52.397 +So yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4736-0 +00:03:53.607 --> 00:03:59.287 +That gives us like the minimum, +and that's a a clean interface. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4767-0 +00:04:00.777 --> 00:04:06.328 +Then basically we would need something +like drop a config JSON and run the + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4767-1 +00:04:06.328 --> 00:04:10.028 +module, +add the config JSON to the resulting repo + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4767-2 +00:04:10.028 --> 00:04:14.617 +as the record of what generated, +and then I think we've done. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4770-0 +00:04:17.567 --> 00:04:18.127 +All right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4781-0 +00:04:18.127 --> 00:04:23.127 +So you still want to have terraform read +from a config dot Jason file. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4798-0 +00:04:24.367 --> 00:04:29.354 +I don't care about the format, +but we will need it to read from some + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4798-1 +00:04:29.354 --> 00:04:30.727 +kind of input, yes. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4804-0 +00:04:34.327 --> 00:04:38.047 +Rather than just having it configured in +the code itself. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4806-0 +00:04:38.707 --> 00:04:39.467 +Well. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4810-0 +00:04:42.177 --> 00:04:43.257 +Again, consider. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4824-0 +00:04:45.337 --> 00:04:48.137 +The least intelligent colleague you've +ever met. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4835-0 +00:04:48.777 --> 00:04:54.181 +Would you want them to go into this +module and tinker with these values + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4835-1 +00:04:54.181 --> 00:04:54.857 +directly? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4850-0 +00:04:54.857 --> 00:04:58.803 +Or would you want them in a place where +they couldn't possibly damage something + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4850-1 +00:04:58.803 --> 00:04:59.937 +they didn't understand? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4871-0 +00:05:03.867 --> 00:05:07.279 +Yeah. OK. +That makes like I totally understand. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4871-1 +00:05:07.279 --> 00:05:12.041 +Hiding some of or, you know, +putting some of this module but don't + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4871-2 +00:05:12.041 --> 00:05:13.747 +exposing it to the user. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4879-0 +00:05:15.597 --> 00:05:18.917 +It's like, +are we ever gonna need to change that? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4910-0 +00:05:19.037 --> 00:05:24.437 +Are we ever going to need to change that +these two values of repository template + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4910-1 +00:05:24.437 --> 00:05:28.504 +and template repo org? +Those are not something that we would + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4901-0 +00:05:26.107 --> 00:05:26.667 +Yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4910-2 +00:05:28.504 --> 00:05:30.637 +expect a user to want to change. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4924-0 +00:05:32.137 --> 00:05:36.217 +So when we're thinking about this +example's basic as the interface. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4926-0 +00:05:36.827 --> 00:05:37.347 +No. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4938-0 +00:05:37.857 --> 00:05:40.097 +You know the same kind of of feedback. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4947-0 +00:05:40.097 --> 00:05:44.817 +We can remove some of the things that we +know we need static values for. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4958-0 +00:05:45.127 --> 00:05:50.167 +Or we can hide things that we know should +not be altered. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4960-0 +00:05:50.487 --> 00:05:50.927 +Yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4985-0 +00:05:51.657 --> 00:05:58.186 +And make this as minimal as possible so +nobody could come in here and be confused + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4985-1 +00:05:58.186 --> 00:06:00.017 +about what our outputs. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/4987-0 +00:06:01.077 --> 00:06:01.797 +Yeah. OK. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5021-0 +00:06:03.367 --> 00:06:08.765 +So I mean I can I can set this up to +where it's requiring a config dot Jason + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5021-1 +00:06:08.765 --> 00:06:14.234 +in your working directory when you call +Terraform apply and just have it read + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5021-2 +00:06:14.234 --> 00:06:16.407 +directly from config dot Jason. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5024-0 +00:06:17.727 --> 00:06:19.407 +That would be that would be fine. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5026-0 +00:06:20.357 --> 00:06:20.797 +OK. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5056-0 +00:06:22.757 --> 00:06:27.635 +And like one of the big things that I +liked about the about the way that we + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5033-0 +00:06:22.857 --> 00:06:23.337 +Alright. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5056-1 +00:06:27.635 --> 00:06:32.705 +were doing it before when we generated +these clusters is that you included the + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5050-0 +00:06:30.397 --> 00:06:30.717 +Yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5056-2 +00:06:32.705 --> 00:06:34.117 +config JSON alongside. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5089-0 +00:06:34.117 --> 00:06:37.389 +So anytime we wanted to regenerate these +clusters, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5059-0 +00:06:34.447 --> 00:06:34.727 +Yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5089-1 +00:06:37.389 --> 00:06:42.649 +all we needed to do was run the function +pointing at the config and it would spit + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5089-2 +00:06:42.649 --> 00:06:44.317 +out the same damn cluster. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5095-0 +00:06:44.317 --> 00:06:47.657 +And that's exactly the experience that +that we're going for. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5118-0 +00:06:49.207 --> 00:06:54.765 +So you do kind of still get that, +except that your config dot JSong isn't + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5118-1 +00:06:54.765 --> 00:06:55.967 +in the repo now. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5127-0 +00:06:55.967 --> 00:07:00.047 +Now it's in the workspace where you're +calling terraform apply from right? So. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5138-0 +00:07:00.507 --> 00:07:03.448 +So OK, +if there's a different workflow that + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5138-1 +00:07:03.448 --> 00:07:05.387 +makes more sense, what is it? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5151-0 +00:07:05.467 --> 00:07:10.427 +Show me 'cause like I this is this is +what's making sense to me. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5157-0 +00:07:10.427 --> 00:07:13.267 +But that's because I have a narrow +perspective, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5175-0 +00:07:13.607 --> 00:07:19.436 +So I'm totally with you on minimizing +what we provide or exposed to the user + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5175-1 +00:07:19.436 --> 00:07:20.647 +for sure, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5173-0 +00:07:20.207 --> 00:07:20.407 +Mm-hmm. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5182-0 +00:07:20.647 --> 00:07:24.047 +That's having the defaults in the module +itself. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5185-0 +00:07:24.477 --> 00:07:24.917 +Yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5196-0 +00:07:25.567 --> 00:07:28.927 +But we actually kinda already did some of +the workflow right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5205-0 +00:07:28.927 --> 00:07:34.098 +Like when you changed the values in +Terraform it updated the files in the + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5205-1 +00:07:34.098 --> 00:07:34.447 +repo. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5207-0 +00:07:34.917 --> 00:07:35.517 +Right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5223-0 +00:07:37.367 --> 00:07:39.528 +And so yeah, I mean, +that's kind of what I was imagining the + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5223-1 +00:07:39.528 --> 00:07:39.847 +workflow. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5238-0 +00:07:39.667 --> 00:07:43.907 +OK. Well and and I OK, +I'm I'm way happy with that. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5246-0 +00:07:43.907 --> 00:07:48.507 +Then my question would be, +where does this artifact get stored? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5249-0 +00:07:51.357 --> 00:07:52.437 +Which artifact? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5264-0 +00:07:52.987 --> 00:07:57.096 +The artifact that was used to generate +the repo that generated the code for the + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5264-1 +00:07:57.096 --> 00:07:57.507 +cluster. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5279-0 +00:07:58.177 --> 00:08:01.768 +I mean that's the Terraform Workspace +where you're calling terraform apply from + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5279-1 +00:08:01.768 --> 00:08:02.217 +right? So. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5295-0 +00:08:02.617 --> 00:08:07.804 +But this is Terraform Ecast deployment +where we'll call all deploys from or all + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5295-1 +00:08:07.804 --> 00:08:08.777 +creations from. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5337-0 +00:08:09.167 --> 00:08:12.419 +Well, I mean, +we're we were training an example + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5307-0 +00:08:10.297 --> 00:08:10.857 +So in here. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5337-1 +00:08:12.419 --> 00:08:15.875 +directory as a workspace so that we could +test it, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5337-2 +00:08:15.875 --> 00:08:21.295 +but in reality we would have a directory +that would have files in it that would + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5337-3 +00:08:21.295 --> 00:08:25.428 +have multiple calls to the SharePoint EKS +deployment module. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5337-4 +00:08:25.428 --> 00:08:27.257 +And that is like where all. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5349-0 +00:08:27.247 --> 00:08:30.127 +The state would live, +and it's where that artifact would live. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5368-0 +00:08:30.167 --> 00:08:34.607 +The artifact being the code itself, +so it's gonna interest to call it the + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5368-1 +00:08:34.607 --> 00:08:37.727 +artifact, +because it's really more like the seed of + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5368-2 +00:08:37.727 --> 00:08:38.327 +it, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5387-0 +00:08:38.437 --> 00:08:43.197 +So you're configuring it just like I +would have made dot TF. Any examples? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5379-0 +00:08:38.717 --> 00:08:39.197 +Right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5380-0 +00:08:41.817 --> 00:08:41.897 +So. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5392-0 +00:08:43.197 --> 00:08:45.157 +Basic directory, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5390-0 +00:08:43.637 --> 00:08:44.077 +Yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5412-0 +00:08:45.197 --> 00:08:48.751 +But you would have a workspace that would +be multiple of those calls, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5412-1 +00:08:48.751 --> 00:08:51.797 +alright and everything would be capturing +code right there. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5422-0 +00:08:53.327 --> 00:08:58.527 +Well, +so if config JSON was in the VAR file. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5431-0 +00:09:00.057 --> 00:09:02.337 +And nothing in here needed to be altered. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5432-0 +00:09:02.537 --> 00:09:03.777 +We'd have the same. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5435-0 +00:09:05.657 --> 00:09:06.617 +Experience. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5446-0 +00:09:09.277 --> 00:09:13.277 +And then you could just have a VAR file +per cluster in this repo. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5461-0 +00:09:15.497 --> 00:09:19.005 +And save it in this repo. +I guess because this repo becomes the + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5461-1 +00:09:19.005 --> 00:09:19.937 +workspace, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5482-0 +00:09:23.627 --> 00:09:27.837 +So it would be a new repo that is +becoming a workspace and that workspace + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5482-1 +00:09:27.837 --> 00:09:30.567 +is calling the Terraform Uks deployment +module. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5484-0 +00:09:31.077 --> 00:09:32.397 +Like multiple times. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5489-0 +00:09:33.257 --> 00:09:34.817 +How would you build that though? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5495-0 +00:09:34.897 --> 00:09:36.457 +How would you build that workspace? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5506-0 +00:09:36.457 --> 00:09:42.257 +I guess I'm confused 'cause I you +differentiate between a workspace and? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5512-0 +00:09:47.007 --> 00:09:49.527 +So like right now the basic directory. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5519-0 +00:09:51.007 --> 00:09:52.607 +We're reading that as a workspace, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5551-0 +00:09:54.207 --> 00:10:00.147 +And we have a call to the teraform uks +module within that workspace and editing + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5551-1 +00:10:00.147 --> 00:10:06.087 +our state and we want to change a value +for the cluster that's being generated. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5567-0 +00:10:06.167 --> 00:10:10.548 +We would do it just by modifying the code +that you see in main dot TF. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5567-1 +00:10:10.548 --> 00:10:11.967 +There right as you see. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5579-0 +00:10:11.567 --> 00:10:17.432 +So, +but what you would not want to do is copy + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5573-0 +00:10:14.037 --> 00:10:14.237 +Hello. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5579-1 +00:10:17.432 --> 00:10:19.727 +basic paste basic. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5582-0 +00:10:21.217 --> 00:10:22.417 +Rename basic. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5588-0 +00:10:24.977 --> 00:10:26.457 +To my new cluster. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5601-0 +00:10:28.727 --> 00:10:30.899 +Yeah, I mean, +you wouldn't have one directory per + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5597-0 +00:10:28.857 --> 00:10:29.497 +And. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5601-1 +00:10:30.899 --> 00:10:31.247 +cluster. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5608-0 +00:10:31.247 --> 00:10:34.687 +You wouldn't be able to have multiple +clusters in a directory. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5609-0 +00:10:37.637 --> 00:10:38.117 +Alright. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5612-0 +00:10:39.937 --> 00:10:40.897 +No, you lost me. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5617-0 +00:10:42.097 --> 00:10:43.937 +OK. Are you still sharing? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5624-0 +00:10:45.137 --> 00:10:49.657 +No. Let me share that again. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5634-0 +00:10:49.737 --> 00:10:53.737 +So yeah, So what I did was I copied basic. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5666-0 +00:10:54.257 --> 00:10:57.871 +I renamed it to my new cluster and then +you know. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5666-1 +00:10:57.871 --> 00:11:03.654 +Then we could have the main TF rewritten +with the values for my new cluster and + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5666-2 +00:11:03.654 --> 00:11:08.497 +that would be one way to maintain it in +Terraform Ecas deployment. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5673-0 +00:11:08.497 --> 00:11:12.577 +But you're telling me? Obviously, +that's not the right way to do it. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5675-0 +00:11:13.107 --> 00:11:13.587 +Yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5704-0 +00:11:14.557 --> 00:11:17.784 +Clearly. +So you're saying we would have a + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5704-1 +00:11:17.784 --> 00:11:22.931 +different repo that would be the +workspaces for this where all the + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5704-2 +00:11:22.931 --> 00:11:26.157 +clusters would be generated that would be. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5697-0 +00:11:24.937 --> 00:11:25.577 +It would. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5714-0 +00:11:25.897 --> 00:11:29.007 +It would be a singular workspace, +but it would be where all the clusters + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5714-1 +00:11:29.007 --> 00:11:29.817 +are generated, yes. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5727-0 +00:11:30.227 --> 00:11:34.467 +Wouldn't that be this platform, TG Infra, +where we link it all in? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5731-0 +00:11:35.957 --> 00:11:37.037 +Yeah, we could do that. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5740-0 +00:11:38.137 --> 00:11:41.137 +Well, I you say that, yeah, +we could do that. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5745-0 +00:11:41.137 --> 00:11:42.937 +Is that not the correct answer? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5748-0 +00:11:43.577 --> 00:11:45.217 +Is it supposed to be something else? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5749-0 +00:11:49.617 --> 00:11:49.737 +Umm. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5766-0 +00:11:54.507 --> 00:11:59.862 +So we were discussing that before, +right in each cluster that's under lab + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5766-1 +00:11:59.862 --> 00:12:00.947 +slash clusters. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5776-0 +00:12:01.627 --> 00:12:05.867 +We were saying before that that could be +a like a get submodule, right? And we. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5782-0 +00:12:05.457 --> 00:12:08.097 +And that's what this is, yes. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5778-0 +00:12:07.217 --> 00:12:07.257 +Are. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5796-0 +00:12:08.417 --> 00:12:12.702 +Yeah, +and that would be each invocation of the + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5796-1 +00:12:12.702 --> 00:12:14.617 +template repo, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5815-0 +00:12:14.617 --> 00:12:19.246 +So each cluster having its own repo that +spawned from the template repo, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5815-1 +00:12:19.246 --> 00:12:23.177 +they would all be cloned into there as +get submodules, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5825-0 +00:12:23.597 --> 00:12:26.477 +Right. And that's what we're doing today. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5821-0 +00:12:25.037 --> 00:12:25.277 +OK. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5828-0 +00:12:26.877 --> 00:12:27.597 +Yeah, totally. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5832-0 +00:12:27.717 --> 00:12:28.637 +So that works. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5841-0 +00:12:28.677 --> 00:12:32.317 +And those are fully the artifacts of +setting it up in Terraform. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5867-0 +00:12:33.937 --> 00:12:38.268 +But like, +if we're in the basic directory right on + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5867-1 +00:12:38.268 --> 00:12:43.617 +uks, that is an example of a workspace. +We only have one call. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5885-0 +00:12:45.297 --> 00:12:49.524 +To to the ECS deployment module on there +and it's not right there that you're + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5885-1 +00:12:49.524 --> 00:12:50.337 +showing, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5884-0 +00:12:50.207 --> 00:12:50.407 +Mm-hmm. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5896-0 +00:12:52.017 --> 00:12:55.137 +We would have a workspace that would have +multiple of these. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5912-0 +00:12:55.607 --> 00:12:58.402 +If you wanna put it closer, +platform PG in front of that, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5912-1 +00:12:58.402 --> 00:12:59.847 +that would totally make sense. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5926-0 +00:13:00.087 --> 00:13:05.613 +We would just have a space where we're +calling this module multiple times, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5926-1 +00:13:05.613 --> 00:13:08.487 +one per cluster. When you get the repo. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5955-0 +00:13:10.017 --> 00:13:13.870 +Where that cluster lives now. +Then you would clone it into there where + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5955-1 +00:13:13.870 --> 00:13:16.257 +you're highlighting CSVD platform lab, +DGA. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5960-0 +00:13:16.937 --> 00:13:20.177 +You would clone that and as a git +submodule. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5963-0 +00:13:22.447 --> 00:13:24.287 +That's what I'm asking is. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5982-0 +00:13:30.977 --> 00:13:35.494 +So what was kind of nice about the Lambda +thing was that we didn't need to have a + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5975-0 +00:13:34.107 --> 00:13:34.307 +Mm-hmm. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5982-1 +00:13:35.494 --> 00:13:37.697 +separate place where stuff lived, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6002-0 +00:13:37.697 --> 00:13:43.417 +Like you would just fire off a payload at +the Lambda and then we would be concerned + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6002-1 +00:13:43.417 --> 00:13:45.937 +about what the Lambda created, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6019-0 +00:13:45.977 --> 00:13:52.078 +And that we would fully clone into the +lab clusters directory there as a + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/5999-0 +00:13:46.287 --> 00:13:46.487 +Mm-hmm. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6019-1 +00:13:52.078 --> 00:13:56.257 +submodule, +but we wouldn't need to also maintain. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6026-0 +00:13:57.017 --> 00:13:58.857 +Like the original source of that stuff, +right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6034-0 +00:13:59.327 --> 00:14:02.247 +Right. But they were in Terraform. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6030-0 +00:13:59.787 --> 00:14:00.427 +Right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6053-0 +00:14:02.247 --> 00:14:06.399 +In Terraform, a stateful. +Now we do need that second place of where + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6053-1 +00:14:06.399 --> 00:14:10.367 +we're managing the state for what +actually created those rebels. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6067-0 +00:14:10.767 --> 00:14:15.207 +So now we have to care about what +generated it and what it generated. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6083-0 +00:14:16.727 --> 00:14:23.664 +So I'm almost thinking we could +essentially create a teragrunt HCL that + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6068-0 +00:14:16.777 --> 00:14:16.857 +So. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6083-1 +00:14:23.664 --> 00:14:25.687 +calls eks deployment. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6087-0 +00:14:27.177 --> 00:14:28.297 +And passes in. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6090-0 +00:14:30.577 --> 00:14:31.777 +The variables. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6096-0 +00:14:34.777 --> 00:14:39.217 +As inputs that would create the. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6103-0 +00:14:40.897 --> 00:14:42.737 +Repository as the 1st. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6107-0 +00:14:45.057 --> 00:14:47.217 +Action before it creates. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6120-0 +00:14:47.647 --> 00:14:50.887 +The cluster, +so essentially this would be like the + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6120-1 +00:14:50.887 --> 00:14:51.967 +bootstrap module. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6127-0 +00:14:55.567 --> 00:14:58.927 +Yeah, you could probably do that, I guess, +yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6134-0 +00:15:00.967 --> 00:15:03.887 +You would still have like the source of +what? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6155-0 +00:15:05.377 --> 00:15:08.952 +Mason is gonna use to generate something, +and then you would have the artifact that + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6155-1 +00:15:08.952 --> 00:15:12.017 +it actually generates and you would still +have to manage both of those. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6165-0 +00:15:13.007 --> 00:15:15.767 +Well, +so and that's that's what I'm thinking. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6168-0 +00:15:15.807 --> 00:15:17.887 +I'm thinking like OK. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6175-0 +00:15:17.887 --> 00:15:22.327 +So we create the the repo directory here. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6186-0 +00:15:24.937 --> 00:15:30.417 +What if I created like a repo HCL that +was? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6203-0 +00:15:32.097 --> 00:15:39.257 +Almost exactly like this, +only instead of calling eks it calls. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6205-0 +00:15:39.257 --> 00:15:41.577 +You know Terraform Ecas deployment. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6214-0 +00:15:42.827 --> 00:15:47.187 +And then we pass in inputs from config +JSON. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6216-0 +00:15:49.237 --> 00:15:49.637 +So. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6229-0 +00:15:51.597 --> 00:15:57.357 +Eks so that this eks module then has a +dependency on. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6241-0 +00:15:59.137 --> 00:16:02.417 +On repo setup or on Ecas deployment I +mean. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6260-0 +00:16:05.577 --> 00:16:10.440 +So what I'm saying is we we could +actually make it like there's a + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6260-1 +00:16:10.440 --> 00:16:12.577 +dependency on, let's call it. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6266-0 +00:16:15.257 --> 00:16:17.457 +You form eks deployment. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6297-0 +00:16:19.877 --> 00:16:26.308 +So that way before we run the uks module, +we run Ecas deployment with the inputs to + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6297-1 +00:16:26.308 --> 00:16:32.357 +generate the repo and then as part of +that it'll start generating the cluster. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6304-0 +00:16:35.707 --> 00:16:38.392 +Yeah, +I don't think that's gonna work the way + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6304-1 +00:16:38.392 --> 00:16:39.267 +you want it to. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6322-0 +00:16:41.137 --> 00:16:47.075 +And I think it would be kind of confusing +because we would have like a circular + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6322-1 +00:16:47.075 --> 00:16:48.857 +dependency sorta, right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6323-0 +00:16:48.927 --> 00:16:49.607 +Also. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6332-0 +00:16:51.347 --> 00:16:56.027 +Our peregrine would be calling Terraform. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6336-0 +00:16:56.227 --> 00:16:58.307 +That would create the repo. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6350-0 +00:16:59.817 --> 00:17:03.577 +That contains the tarragon that we're +running when we run tarragon. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6357-0 +00:17:05.487 --> 00:17:07.847 +Oh, yeah, yeah, yeah. OK. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6360-0 +00:17:07.847 --> 00:17:08.807 +I see what you're saying. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6366-0 +00:17:10.487 --> 00:17:11.767 +Really. That's amazing, dude. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6372-0 +00:17:11.767 --> 00:17:13.927 +I'm surprised you follow that 'cause +that's confusing. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6375-0 +00:17:13.927 --> 00:17:15.607 +I have a lot of myself saying that. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6381-0 +00:17:17.077 --> 00:17:20.237 +No, no. How would I phrase that? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6400-0 +00:17:23.897 --> 00:17:28.198 +The artifacts would be present on disk +during the evaluation phase of Terra + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6386-0 +00:17:24.387 --> 00:17:24.667 +Hello. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6400-1 +00:17:28.198 --> 00:17:28.537 +Grand. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6427-0 +00:17:32.367 --> 00:17:35.675 +So. +So because the first module is the + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6427-1 +00:17:35.675 --> 00:17:41.102 +creation of the other modules until the +1st module is executed, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6427-2 +00:17:41.102 --> 00:17:45.767 +the other modules don't exist on disk to +be evaluated. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6436-0 +00:17:45.807 --> 00:17:48.487 +So you wouldn't be able to orchestrate +between them. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6432-0 +00:17:46.177 --> 00:17:46.577 +Yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6438-0 +00:17:48.967 --> 00:17:49.367 +Thought. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6440-0 +00:17:49.007 --> 00:17:49.887 +Yeah, I get you. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6444-0 +00:17:51.327 --> 00:17:52.767 +OK, OK. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6450-0 +00:17:52.767 --> 00:17:55.807 +Yeah. So that's a bad idea, +and that's fine. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6453-0 +00:17:57.477 --> 00:17:58.197 +That's fine. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6460-0 +00:17:58.197 --> 00:18:00.797 +So, OK, so then rewinding? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6476-0 +00:18:02.387 --> 00:18:07.654 +I think we just need the the simpler +interface into your module and we'll call + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6476-1 +00:18:07.654 --> 00:18:08.187 +it good. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6481-0 +00:18:09.087 --> 00:18:10.407 +Alright, sweet. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6480-0 +00:18:10.257 --> 00:18:10.937 +Sound good? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6488-0 +00:18:11.327 --> 00:18:14.304 +Yeah. +Do you want me to set up a workspace for + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6488-1 +00:18:14.304 --> 00:18:15.127 +this, though? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6491-0 +00:18:17.027 --> 00:18:18.227 +Is that the right answer? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6494-0 +00:18:18.267 --> 00:18:19.627 +Is that what we should do? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6497-0 +00:18:20.577 --> 00:18:21.857 +I think so. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6499-0 +00:18:22.187 --> 00:18:22.867 +Then yes. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6522-0 +00:18:23.467 --> 00:18:27.216 +Yeah, +right now you and I are working in like + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6506-0 +00:18:25.687 --> 00:18:25.967 +How? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6522-1 +00:18:27.216 --> 00:18:32.187 +the basic directory and you have. Yeah. +Yeah, totally, yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6518-0 +00:18:29.657 --> 00:18:31.377 +Which we should right? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6549-0 +00:18:32.187 --> 00:18:36.520 +I mean like you have your local values +stored there and I have my local values + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6549-1 +00:18:36.520 --> 00:18:40.799 +and that's what's allowing us to each +create a repo that we can check out and + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6549-2 +00:18:40.799 --> 00:18:41.347 +test with. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6578-0 +00:18:42.857 --> 00:18:47.959 +So yeah, once I create a workspace, +we will have a place where we can still + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6578-1 +00:18:47.959 --> 00:18:51.248 +both work, +but it will be a shared space for all + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6578-2 +00:18:51.248 --> 00:18:54.537 +modules and you covering values for main +dot TF. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6574-0 +00:18:52.367 --> 00:18:52.567 +Right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6603-0 +00:18:55.047 --> 00:18:59.561 +The basic directory right now if you +check that in and I pulled it like, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6603-1 +00:18:59.561 --> 00:19:04.447 +my values would be updated to reflect +yours and we have collisions, right? So. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6598-0 +00:19:02.337 --> 00:19:02.857 +Right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6626-0 +00:19:04.707 --> 00:19:08.463 +Right. +And that and that was my concern like how + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6626-1 +00:19:08.463 --> 00:19:14.594 +how do we create this in such a way that +we don't have to worry about trampling + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6626-2 +00:19:14.594 --> 00:19:16.587 +over each other over time. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6628-0 +00:19:16.937 --> 00:19:17.617 +Yeah, exactly. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6630-0 +00:19:18.057 --> 00:19:18.417 +Yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6664-0 +00:19:19.017 --> 00:19:21.992 +Can you send me your copy of Maine dot TF? +And yeah, + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6664-1 +00:19:21.992 --> 00:19:25.922 +I'll go ahead and put together a +workspace and I'll use both of these + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6641-0 +00:19:22.387 --> 00:19:22.787 +Yeah. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6664-2 +00:19:25.922 --> 00:19:28.673 +clusters. +The one that you have here and the one + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6664-3 +00:19:28.673 --> 00:19:32.097 +that I have in my version of this, +and I'll put that in the. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6674-0 +00:19:32.097 --> 00:19:34.577 +Workspace so that we can have more +concrete example of that. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6675-0 +00:19:35.147 --> 00:19:35.427 +OK. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6680-0 +00:19:36.977 --> 00:19:37.777 +Sounds good. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6682-0 +00:19:37.007 --> 00:19:39.087 +Wait right on, man. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6686-0 +00:19:40.817 --> 00:19:41.657 +Thanks for your time. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6688-0 +00:19:41.087 --> 00:19:41.727 +All right. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6692-0 +00:19:42.007 --> 00:19:43.207 +Yeah. No, no problem. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6694-0 +00:19:43.207 --> 00:19:43.647 +No problem. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6702-0 +00:19:43.687 --> 00:19:45.927 +And I'm sorry I've been in such a pain to +get ahold of. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6704-0 +00:19:46.427 --> 00:19:46.867 +Rachel. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6710-0 +00:19:47.777 --> 00:19:49.617 +Do you want to do this again tomorrow? + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6713-0 +00:19:51.827 --> 00:19:52.827 +Yes, sure, man. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6721-0 +00:19:53.097 --> 00:19:55.177 +Because that way we'll do it as a dry run. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6727-0 +00:19:55.177 --> 00:19:57.977 +For whatever we demo on Wednesday. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6729-0 +00:19:58.147 --> 00:19:59.347 +Yep, for sure. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6731-0 +00:19:59.587 --> 00:19:59.987 +Cool. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6737-0 +00:20:00.617 --> 00:20:01.937 +Right on, man. Thank you, Duke. + +34f0ecc1-4d22-45f5-b426-d851f282ce5d/6738-0 +00:20:01.667 --> 00:20:03.227 +All right, dude. Have a good evening. \ No newline at end of file diff --git a/docs/callnotes-actionitems-09152025.md b/docs/callnotes-actionitems-09152025.md new file mode 100644 index 0000000..e5c98d3 --- /dev/null +++ b/docs/callnotes-actionitems-09152025.md @@ -0,0 +1,66 @@ +# Call Notes & Action Items - September 15, 2025 + +## Summary +Discussion between David John Arnold Jr. and Matthew Creal Morgan regarding improvements to the terraform-eks-deployment module. The main focus was on simplifying the interface for users, consolidating naming variables, and establishing a better workflow for managing multiple EKS clusters. + +## Action Items + +1. **Simplify Module Interface** + - Reduce the number of variables exposed to users + - Use the config_json structure as a model for the interface + - Remove duplicate/redundant variables (e.g., repository name and cluster name should be unified) + - Status: ✅ In Progress + +2. **Consolidate Naming Variables** + - Use a single `name` variable for both repository and cluster names + - Remove `cluster_name` from the `cluster_config` object + - Update all templates to reference the top-level `name` variable + - Status: ✅ Completed + +3. **Remove Unnecessary Variables** + - Remove `aws_profile` as it can be built dynamically from account name and ID + - Remove `enable_all_modules` as it should be a default assumption + - Status: 🔄 To Do + +4. **Update GitHub Repository Source** + - Change source from `"terraform-github-repo"` to `"git::git@github.e.it.census.gov:CSVD/terraform-github-repo.git"` + - Status: ✅ Completed + +5. **Create a Workspace for Multiple Clusters** + - Set up a shared workspace that will manage multiple clusters + - Avoid using separate directories that would cause conflicts between users + - David to create this workspace with examples from both David and Matthew + - Status: 🔄 To Do + +6. **Variable Values** + - Keep static values like `eks_instance_disk_size`, `eks_ng_desired_size`, etc. with sensible defaults in the module + - Only expose variables that users actually need to modify + - Status: 🔄 To Do + +7. **Demo Preparation** + - Schedule a follow-up meeting for September 16, 2025, to do a dry run + - Prepare for a demonstration on Wednesday, September 17, 2025 + - Status: 📅 Scheduled + +## Implementation Strategy + +### Phase 1: Module Interface Cleanup +- Refine the variables.tf file to remove redundant fields +- Update examples to reflect the new, simplified interface +- Ensure backward compatibility or provide migration path + +### Phase 2: Workspace Structure +- Create a centralized workspace for managing multiple clusters +- Demonstrate how multiple clusters can be managed without conflicts +- Document the approach for the team + +### Phase 3: Documentation and Demo +- Create clear documentation on the new workflow +- Prepare demonstration materials +- Conduct dry run on September 16 +- Present to wider team on September 17 + +## Notes +- The discussed approach uses Terraform rather than Lambda for deployment +- State management is a key consideration as we need to track both what created the repos and what the repos contain +- Need to ensure we maintain proper references to the created resources for future updates \ No newline at end of file