You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Integrate usage of neptune graph SDK for schema queries and lambda logic (#5)
Introduce usage of the neptune graph (analytics) SDK in a couple scenarios: 1. during pipeline creation, if an axios request fails when querying the Neptune Analytics graph and falls back to SDK and 2. if the user has opted to use SDK for the generated lambda (as opposed to http).
Summary of changes:
-added new dependency on client-neptune-graph version 3.662.0
-created new lambda template which is used if the user specifies --output-resolver-query-sdk option
-set additional lambda environment variable for neptune db name which is required to execute queries using the neptune graph SDK
-added logic to fall back to neptune graph SDK if Axios request fails during pipeline creation (previous logic threw Error as the analytics SDK was not yet available)
-fixed function which retrieves graph summary to use neptune graph SDK if the neptune-type is neptune-graph (the summary endpoint path for neptune-db is not the same for neptune-graph)
-fixed CDK pipeline to only fetch cluster info if the type is neptune-db as it is not required for Neptune-graph (analytics)
-set isNeptuneIAMAuth to true if the neptune type is detected as neptune-graph
-introduced util.js for parsing functions that are used across multiple modules
-refactored function which had many params to use an object param instead for better readability
-fixed some typos which specified 'neptume' instead of 'neptune'
-changed queryNeptune function to have default value of empty object for params
-change jest config from json to js to allow for globals to be set from environment variables
-changed test cases to reference <AIR_ROUTES_DB_HOST> and <AIR_ROUTES_DB_PORT values which are swapped at test runtime for the environment variable values for easier test configurability and to prevent future accidental commit of real URLs
-removed duplicated airports.source.schema.graphql file in test cases and changed to reference single file in parent directory
-fixed Case05/case02.json which I believe was accidentally changed from remove to create pipeline
-introduced new test case 7 which sets --output-resolver-query-sdk option
Copy file name to clipboardexpand all lines: doc/cliReference.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ It removes the pipeline created with `--create-update-aws-pipeline`. The resourc
135
135
<br>
136
136
This trigger the creation of a CDK file to be use to create the AWS resources for the GraphQL API, including the AppSync GraphQL API and the Lambda that run the resolver.
This set the Neptune database endpoint used by the Lambda function to query the Neptune database. If not set it used the endpoint set with `--input-graphdb-schema-neptune-endpoint`.
0 commit comments