Fix: Add Terraform resource name validation - #10
Open
Ryan-825 wants to merge 1 commit into
Open
Conversation
- Add validate_terraform_name() function to reject hyphenated names - Integrate validation into import_resource, import_batch, and generate_import_script - Add comprehensive test suite with 12 tests covering valid/invalid names - Generate diagnostic build logs for the fix
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds explicit validation for Terraform resource names before import, dry-run, and generated script output. Invalid names (especially hyphenated ones) are rejected with actionable error messages instead of invoking Terraform with unsafe addresses.
Changes
Testing
Checklist