Skip to content
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/aws: db_parameter_group name validation #3279

Merged
merged 1 commit into from
Oct 8, 2015

Conversation

stack72
Copy link
Contributor

@stack72 stack72 commented Sep 18, 2015

Adding a small note to the docs for db_parameter_group to show it needs to be lowercase. The use of UpperCase characters will continually show changes to the resource

This was reported in IRC http://paste.in.ua/543/

@stack72 stack72 changed the title [DOCS] AWS db_parameter_group name update AWS db_parameter_group name validation Sep 18, 2015
@stack72 stack72 changed the title AWS db_parameter_group name validation provider/aws: db_parameter_group name validation Sep 28, 2015
@radeksimko
Copy link
Member

radeksimko added a commit that referenced this pull request Oct 8, 2015
provider/aws: db_parameter_group name validation
@radeksimko radeksimko merged commit 96dc244 into hashicorp:master Oct 8, 2015
@stack72 stack72 deleted the aws-db_param_group_lowercase branch October 8, 2015 08:40
@apparentlymart
Copy link
Contributor

Regarding the requirement for lowercase:

In some other similar cases recently (#3120 and #3235) we addressed the "stored as lowercase" issue by normalizing rather than validating the string. In those cases AWS doesn't reject a string with uppercase letters, but rather just converts them to lowercase.

I thought doing the same thing in Terraform was the right choice because it allows the name to be produced by interpolating something that might contain uppercase letters and have that be accepted. I'm not sure if such an approach is appropriate here too, but figured I'd point this out in the interests of consistency.

@stack72
Copy link
Contributor Author

stack72 commented Oct 8, 2015

@apparentlymart I agree there are inconsistencies across the codebase for this. I guess a decision can be made on what needs to happen to it and I will gladly change the code

I will defer this decision to you folks though

@radeksimko
Copy link
Member

I thought doing the same thing in Terraform was the right choice because it allows the name to be produced by interpolating something that might contain uppercase letters and have that be accepted. I'm not sure if such an approach is appropriate here too, but figured I'd point this out in the interests of consistency.

I hear you there, I've been always advocating for stricter checks, so that the DSL/code will equal to the reality and less magic happens.

@ghost
Copy link

ghost commented Apr 30, 2020

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.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants