Skip to content

fix: extend resource naming check to all providers#1041

Open
james00012 wants to merge 2 commits intomasterfrom
check-resource-naming-gcp
Open

fix: extend resource naming check to all providers#1041
james00012 wants to merge 2 commits intomasterfrom
check-resource-naming-gcp

Conversation

@james00012
Copy link
Contributor

Summary

  • check-resource-naming.sh only validated AWS resources. Now dynamically discovers all <provider>/resources/ directories so GCP (and future providers) are covered automatically.
  • Added guard clauses for empty grep results to prevent silent failures under set -euo pipefail.
  • Added YAML tag count to output for parity with the resource type summary.

Test plan

  • bash scripts/check-resource-naming.sh passes and reports 121 resource types + 128 YAML tags

@james00012 james00012 requested a review from denis256 as a code owner March 8, 2026 17:32
- Add empty CONFIG_BLOCK guard to prevent silent false-pass if the
  Config struct signature changes or config.go is malformed
- Add scanning output showing which directories are checked for
  easier debugging
@james00012 james00012 force-pushed the check-resource-naming-gcp branch from 858f5e2 to 16e66c7 Compare March 10, 2026 00:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant