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

allow spaces in db subnet name #3955

Merged
merged 1 commit into from Nov 17, 2015
Merged

Conversation

cbusbey
Copy link
Contributor

@cbusbey cbusbey commented Nov 17, 2015

fixes #3954

@radeksimko
Copy link
Member

screen shot 2015-11-21 at 12 39 04

I think the comment above the test with links to other similar issues is worth more than any other comment.

Thanks for sending the patch! 👍

I will notify AWS. Apparently they have fixed AWS CLI docs last time when I was reporting dots & underscores: http://docs.aws.amazon.com/cli/latest/reference/rds/create-db-subnet-group.html but forgot completely about the API docs ^

radeksimko added a commit that referenced this pull request Nov 17, 2015
@radeksimko radeksimko merged commit 306046b into hashicorp:master Nov 17, 2015
@cbusbey cbusbey deleted the db_subnet_spaces branch November 18, 2015 14:19
@ghost
Copy link

ghost commented Apr 29, 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.

@hashicorp hashicorp locked and limited conversation to collaborators Apr 29, 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.

aws_db_security_group should allow spaces
2 participants