-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
neptune: specify port for the cluster #31074
neptune: specify port for the cluster #31074
Comments
Looking at DatabaseClusterProps, there appears to be no property that maps to @badmintoncryer Thanks for submitting the feature request. Kindly note that aws-neptune-alpha is an experimental L2 construct as of now, so we encourage community to submit updates to this construct package. Feel free to submit PR that could be reviewed by the team. Thanks, |
Comments on closed issues and PRs are hard for our team to see. |
1 similar comment
Comments on closed issues and PRs are hard for our team to see. |
### Issue # (if applicable) Closes aws#31074. ### Reason for this change Cloudformation supports for setting port number for the Neptune cluster but AWS CDK cannot do this. ### Description of changes Add `port` prop to `DatabaseClusterProps`. ### Description of how you validated changes Added both unit and integ tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
### Issue # (if applicable) Closes aws#31074. ### Reason for this change Cloudformation supports for setting port number for the Neptune cluster but AWS CDK cannot do this. ### Description of changes Add `port` prop to `DatabaseClusterProps`. ### Description of how you validated changes Added both unit and integ tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
### Issue # (if applicable) Closes #31074. ### Reason for this change Cloudformation supports for setting port number for the Neptune cluster but AWS CDK cannot do this. ### Description of changes Add `port` prop to `DatabaseClusterProps`. ### Description of how you validated changes Added both unit and integ tests. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Describe the feature
Specify port number of the Neptune cluster.
Use Case
We can configure the port number of Neptune cluster but CDK L2 construct cannot configure this.
Proposed Solution
Add
port
property toDatabaseClusterProps
and set DBPort to theport
value.https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-neptune-dbcluster.html#cfn-neptune-dbcluster-dbport
Other Information
No response
Acknowledgements
CDK version used
2.150.0
Environment details (OS name and version, etc.)
irrelevant
The text was updated successfully, but these errors were encountered: