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
Added ability to create Apollo zip using an input graphQL schema file instead of discovering the schema by querying neptune. For consistency with App Sync pipeline and CDK workflows, this workflow requires setting a new endpoint argument --create-update-apollo-server-neptune-endpoint in addition to the existing --input-schema-file argument.
Other changes:
-fixed bugs resolving gremlin queries and added resolver tests for these scenarios
-changed schema file in zip to have output. prefix for consistency with the resolver file
-bumped the version from 1.1.1 to 1.2.0-beta.1
Copy file name to clipboardexpand all lines: README.md
+11-2
Original file line number
Diff line number
Diff line change
@@ -275,15 +275,24 @@ See CDK end to end example [here](https://github.com/aws/amazon-neptune-for-grap
275
275
# Generate Apollo Server Artifacts
276
276
If you prefer to use Apollo Server instead of AWS App Sync, the utility can generate a ZIP file of Apollo Server artifacts with the CLI option `--create-update-apollo-server` for a standalone server or `--create-update-apollo-server-subgraph` for federated systems.
277
277
278
-
For example:
278
+
Example of starting with a neptune database with data from which to determine the graphQL schema:
The example commands above will generate the file `apollo-server-<identifier>-<timestamp>.zip`, which can then be deployed locally by following these steps:
0 commit comments