-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provider enforcing only lowercase alphanumeric characters and hyphens allowed in parameter group "name" makes importing impossible #12144
Comments
Similar: @iMartyn Please try using the lifecycle {
ignore_changes = ["name"]
} |
Hi @ewbankkit, I have the same issue with importing aws_db_option_group. The |
When attempting to modify a default RDS DB parameter group in the AWS management console I get:
So, for my purposes, there's no point in managing the DB parameter group state since it seems to be immutable. For the purpose of assigning the parameter group to a DB, perhaps it's also irrelevant since it gets assigned in the absence of an explicit DB parameter group? A little bit of explicitness is sacrificed but nothing that leaving a comment stating that the default DB parameter group is intentionally being used wouldn't address. For me the biggest downside has been that it was confusing to run into, so maybe something in the docs then? |
Similar situation for option groups - trying to import an option group named |
Facing same issue . Any update on this? |
With big noise Hashicorp announced a release of Terraform 1.0. And it was released with the errors that were reported a year ago and to fix which just tiny change in one line code with regexp needed. |
@voroniys This is an issue in the provider, not core terraform |
Issue still exists:
This is imported resource and the value is: default.postgres13 in aws |
I am encountering the same issue with a parameter group that is attached to a Redshift cluster. I am using the default in aws which is |
I am working on this now. It is a little bit mind boggling that no one has decided to take this on yet, the fix is simple and this is clearly a high priority. @iMartyn |
This functionality has been released in v5.21.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Terraform Version
Terraform v0.12.21 (same with 0.12.20)
Affected Resource(s)
Terraform Configuration Files
Debug Output
Partial output https://gist.github.com/iMartyn/09aea39aff770335ce533ca3373a27c0#file-terraform-debug-txt - too much useful information to others in the full output to make that public.
Panic Output
No panic, just errors
Expected Behavior
Given that this resource exists on aws, I should be able to import it into terraform.
Actual Behavior
Cannot execute plan
Steps to Reproduce
terraform plan
Important Factoids
The DB was pre-existing, I'm trying to import everything into terraform that has been created by point-and-click.
References
I'm not the only one facing this problem :
https://stackoverflow.com/questions/57386371/terraform-rds-instance-errors-with-lowercase-alphanumeric-characters-and-hypens
The text was updated successfully, but these errors were encountered: