belt 0.3.30 → 0.3.31

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 79ffa332a2eb6408d42c4652d1643009edac470adb6eabbcb9e6818286276977
-  data.tar.gz: 145edae1f0f725c16232a648d64ad3224ac93baca18273648b901e7d4ef6ad66
+  metadata.gz: b3545e62c7890adc16931218212e284d8e68994814be13ae0e231d5aee89b2ec
+  data.tar.gz: 89b19c24b919d441bffbbb8cd426697e656b8726596c24c58cf5f03d79233c81
 SHA512:
-  metadata.gz: '09e7a47ed0e3d34e699cbd2e1c14785399015ea66cde8b21dfd194e86d09456df246da0363e0bc0e543ad06129938376c148e87edc6885b0b6c9d94645ffdcd3'
-  data.tar.gz: 16ec119be87259081c896497229cf3202901c3657ac4aea2f3e47e05ff3976d7130e23a99dcdf1c85b80f8d386243878e0acccd4bc9cb721b0ca8d8e189e4122
+  metadata.gz: 7df1d7c18c7208d54cb0e37cbea0cf6c998f9b502950651c7e3e304f2786c3a750d664894d5f7f09cbc8848b550f365d7ebe415a5bcb701da45ef115fb7d28bb
+  data.tar.gz: '05380ceae6d72a8874e66f52f616b527baa69f7101513842a6240765d2b1b6644bcd7b6d469acffeab246d18a152eabfb618a52c74753f5e61fd8cbbb663143a'

data/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.3.31
+
+### Bug Fix
+
+- **`belt destroy environment` now uses the environment's AWS profile**: The
+  terraform destroy path (and remote-state detection) previously inherited
+  whatever `AWS_PROFILE` was in the shell, which could point at the wrong
+  account and fail with "No valid credential sources found". It now loads
+  `infrastructure/<env>/belt.rb` and applies the configured `aws_profile` and
+  env vars before running terraform — matching `belt deploy` and
+  `belt terraform`.
+
 ## 0.3.16
 
 ### Enhancement

data/lib/belt/cli/destroy_command.rb

@@ -6,6 +6,7 @@ require_relative 'auth_command'
 require_relative 'frontend_registry'
 require_relative 'generator_registry'
 require_relative 'tables_command'
+require_relative 'environment_config'
 require_relative '../inflector'
 
 module Belt
@@ -214,6 +215,13 @@ module Belt
           end
         end
 
+        # Apply the environment's AWS profile + env vars from infrastructure/<env>/belt.rb
+        # BEFORE any terraform/aws calls, so both remote-state detection and the
+        # subsequent destroy authenticate against the correct account. Without this,
+        # terraform inherits whatever AWS_PROFILE is in the shell, which may point at
+        # the wrong account (mirrors `belt deploy` / `belt terraform`).
+        apply_env_config! unless @skip_terraform
+
         # Check if terraform state exists (infra may still be live)
         if !@skip_terraform && terraform_state_exists?(dir)
           puts "⚠  Environment '#{@name}' appears to have active infrastructure."
@@ -380,6 +388,15 @@ module Belt
         puts '  ✓ Infrastructure destroyed.'
       end
 
+      # Load infrastructure/<env>/belt.rb and apply its aws_profile + env vars to
+      # the current process so terraform (and any aws CLI calls during destroy)
+      # authenticate against the right account. Mirrors DeployCommand / TerraformCommand.
+      def apply_env_config!
+        env_config = EnvironmentConfig.load(@name)
+        env_config.apply!
+        puts "  🔑 Using AWS profile: #{env_config.aws_profile}" if env_config.aws_profile?
+      end
+
       def empty_s3_buckets_in_state
         output = `terraform state list 2>/dev/null`
         return unless Process.last_status.success?

data/lib/belt/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Belt
-  VERSION = '0.3.30'
+  VERSION = '0.3.31'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: belt
 version: !ruby/object:Gem::Version
-  version: 0.3.30
+  version: 0.3.31
 platform: ruby
 authors:
 - Stowzilla