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

Error: aws_elasticache_cluster.xxxxxx: "port": required field is not set #4149

Closed
aprice opened this issue Apr 10, 2018 · 4 comments
Closed
Labels
bug Addresses a defect in current functionality. service/elasticache Issues and PRs that pertain to the elasticache service.

Comments

@aprice
Copy link

aprice commented Apr 10, 2018

Terraform Version

Terraform v0.11.6
+ provider.aws v0.1.4

Affected Resource(s)

aws_elasticache_cluster

Expected Behavior

Per the documentation:

port – (Optional) The port number on which each of the cache nodes will accept connections. For Memcache the default is 11211, and for Redis the default port is 6379. Cannot be provided with replication_group_id.

Actual Behavior

Not specifying a port yields an error:

Error: aws_elasticache_cluster.xxxxxx: "port": required field is not set

I'm not sure if it's the documentation that's wrong or the behavior, but the two definitely do not agree.

@catsby
Copy link
Contributor

catsby commented Apr 10, 2018

Hey @aprice  , could you share a config that reproduces this? We have a handful of nightly tests that do not specify a port and they are passing.

@catsby catsby added bug Addresses a defect in current functionality. waiting-response Maintainers are waiting on response from community or contributor. labels Apr 10, 2018
@bflad
Copy link
Contributor

bflad commented Apr 10, 2018

The switch from the port attribute being required to optional happened in #3835 and was released in version 1.13.0 of the AWS provider.

@bflad bflad added the service/elasticache Issues and PRs that pertain to the elasticache service. label Apr 10, 2018
@bflad
Copy link
Contributor

bflad commented May 31, 2018

Closing due to lack of response -- if this is still an issue after version 1.13.0 of the AWS provider or higher, please let us know.

@ghost
Copy link

ghost commented Apr 5, 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 5, 2020
@breathingdust breathingdust removed the waiting-response Maintainers are waiting on response from community or contributor. label Sep 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/elasticache Issues and PRs that pertain to the elasticache service.
Projects
None yet
Development

No branches or pull requests

4 participants