-
-
Notifications
You must be signed in to change notification settings - Fork 557
Comparing changes
Open a pull request
base repository: sous-chefs/aws
base: 9.2.2
head repository: sous-chefs/aws
compare: main
- 12 commits
- 15 files changed
- 4 contributors
Commits on Sep 4, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 4899d1c - Browse repository at this point
Copy the full SHA 4899d1cView commit details
Commits on Sep 5, 2025
-
Standardise files with files in sous-chefs/repo-management (#504)
Signed-off-by: kitchen-porter <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 7b41e59 - Browse repository at this point
Copy the full SHA 7b41e59View commit details
Commits on Sep 10, 2025
-
Update sous-chefs/.github action to v4 (#506)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 0b50173 - Browse repository at this point
Copy the full SHA 0b50173View commit details
Commits on Sep 17, 2025
-
Standardise files with files in sous-chefs/repo-management (#508)
Signed-off-by: kitchen-porter <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for a208266 - Browse repository at this point
Copy the full SHA a208266View commit details
Commits on Sep 19, 2025
-
Standardise files with files in sous-chefs/repo-management (#509)
Signed-off-by: kitchen-porter <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 402aee8 - Browse repository at this point
Copy the full SHA 402aee8View commit details
Commits on Oct 14, 2025
-
fix(ci): Update workflows to use release pipeline (#513)
* feat(ci): migrate to reusable workflows v4.1.0 Update ci.yml to use lint-unit workflow v4.1.0 Add conventional-commits workflow for PR validation Add prevent-file-change workflow for metadata protection Add release workflow using release-cookbook v4.1.0 Add release-please configuration files Use secrets: inherit for proper secret propagation * fix(ci): Update workflows to use release pipeline Signed-off-by: Dan Webb <[email protected]> --------- Signed-off-by: Dan Webb <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 45a6485 - Browse repository at this point
Copy the full SHA 45a6485View commit details -
Configuration menu - View commit details
-
Copy full SHA for 16681e7 - Browse repository at this point
Copy the full SHA 16681e7View commit details
Commits on Oct 15, 2025
-
fix(ci): Update CHANGELOG list formatting (#519)
* feat(cloudwatch): Add treat_missing_data property to cloudwatch alarms Signed-off-by: Dan Webb <[email protected]> * fix(ci): Update CHANGELOG list formatting Signed-off-by: Dan Webb <[email protected]> * chore(docs): Remove empty changelog entries Signed-off-by: Dan Webb <[email protected]> --------- Signed-off-by: Dan Webb <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 7e8c191 - Browse repository at this point
Copy the full SHA 7e8c191View commit details -
feat(cloudwatch): Add treat_missing_data property to cloudwatch alarms (
#515) Signed-off-by: Dan Webb <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 304af1e - Browse repository at this point
Copy the full SHA 304af1eView commit details -
Fix AWS region detection for GovCloud regions in aws cookbook (#518)
## Summary Fix AWS region detection for GovCloud regions (us-gov-east-1, us-gov-west-1) by using the region directly from EC2 metadata instead of incorrectly parsing it from the availability zone. ## Why The previous implementation had a bug in the fallback_region method that attempted to derive the region from the availability zone by: 1. Chopping the last character from the AZ (e.g., us-gov-east-1a -> us-gov-east-1) 2. If the AZ had more than 3 dashes, it would truncate to only the first 3 parts This caused GovCloud regions like `us-gov-east-1` to be incorrectly truncated to us-gov-east, resulting in DNS resolution failures when trying to connect to AWS APIs: `Failed to open TCP connection to ec2.us-gov-east.amazonaws.com:443` (getaddrinfo: Name or service not known) The fix uses `node['ec2']['region']` directly from Ohai EC2 metadata, which already provides the correct region format for all AWS regions including GovCloud. Added debug logging to show both the correct region and what the old logic would have returned for troubleshooting. Co-authored-by: Dan Webb <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for b935827 - Browse repository at this point
Copy the full SHA b935827View commit details -
chore(main): release 9.3.0 (#520)
Co-authored-by: Dan Webb <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d3af5e2 - Browse repository at this point
Copy the full SHA d3af5e2View commit details
Commits on Nov 20, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 37476e6 - Browse repository at this point
Copy the full SHA 37476e6View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 9.2.2...main