Make the "Family" property of "NeptuneDBParameterGroup" resource configurable via installer

[jaychung-aws]

Aws Connected Device Framework Affected Module(s): asset-library

I'm submitting a ...

• [X] bug report
• [ ] feature request

Description:

Clone the main branch and deploy asset-library using db.t3.medium as the instance type with default settings. Deployment of the cdf-assetlibrary-neptune-${env} fails with error stating:

Resource handler returned message: "The Parameter Group neptunedbclusterparametergr-zkzjqpysw2bt with DBParameterGroupFamily neptune1.2 cannot be used for this instance. Please use a Parameter Group with DBParameterGroupFamily neptune1.3 (Service: Neptune, Status Code: 400, Request ID: e188f555-3e47-4ee1-aae6-fb9586d2c2ce)" (RequestToken: 19c1e8e8-a998-461a-d329-e930111af65c, HandlerErrorCode: InvalidRequest)

Current behavior:

Deployment fails with CloudFormation throwing an exception stating the Family parameter of the DBClusterParameterGroup resource must be neptune1.3. In the cfn-neptune.yaml today, this is hard-coded to neptune1.2.

Expected behavior:

Deployment of asset-library should not fail. Consider making the Family parameter of DBClusterParameterGroup resource configurable via wizard prompt and also via the cdf-cli configuration JSON file that is generated on successful deployment.

Steps to reproduce:

1. Clone the main branch of the open source CDF repo.
2. Use the installer wizard to deploy asset-library with instance type set to db.t3.medium, leaving other settings as default.

Additional Information: https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html

[aaronatbissell]

Agreed - this makes sense for backwards compatibility as well. We are still using neptune1