Document GraphQL API for GA release

modules/ROOT/content-nav.adoc

@@ -57,12 +57,11 @@
 * *Products*
 
 * xref:aura-graphql/index.adoc[]
-** xref:aura-graphql/prerequisites.adoc[]
-** xref:aura-graphql/deploy-and-operate.adoc[]
-** xref:aura-graphql/authentication-providers.adoc[]
-** xref:aura-graphql/using-your-api.adoc[]
-** xref:aura-graphql/end-of-beta-phase.adoc[]
-
+** xref:aura-graphql/api-creation.adoc[]
+** xref:aura-graphql/api-update.adoc[]
+** xref:aura-graphql/api-deletion.adoc[]
+** xref:aura-graphql/api-usage.adoc[]
+** xref:aura-graphql/aura-cli-configuration.adoc[]
 
 * xref:introspector.adoc[Introspector]
 

modules/ROOT/pages/aura-graphql/api-creation.adoc

@@ -0,0 +1,162 @@
+= Creating a GraphQL API
+
+
+== Before you start
+
+Make sure that you have:
+
+* The ID, username and password for the AuraDB.
+* Your type definitions.
+* If you intend to use JWKS for authentication, the URL from your identity provider that will be used to verify JWKS tokens.
+
+If you intend to use the Aura CLI, follow the guidance provided in xref:aura-graphql/aura-cli-configuration.adoc[] before proceeding.
+
+
+== Console
+
+. In the Aura Console, select **Data APIs** from the left side navigation.
+. Use **Create API** and fill in the details in the **Create GraphQL Data API** dialog.
++
+image::aura-graphql/create/details.png[]
++
+[CAUTION]
+====
+If you set **Enable introspection** and **Enable field suggestions** for production systems the information they provide can be used by malicious actors to reverse-engineer your GraphQL schema and execute arbitrary operations.
+
+**Enable introspection** allows you to query the schema and discover the available queries, mutations, subscriptions, types and fields in the GraphQL API.  
+
+**Enable field suggestions** provides suggestions that hint towards GraphQL typos.
+Even with just field suggestions enabled, it is possible for a malicious actor to discover your entire schema.
+====
++
+. Type definitions
++
+This is where you describe the graph database in the AuraDB that the GraphQL API will be used with.
+The Type Definitions are the same as those used with Neo4j GraphQL Library with the exception that custom resolvers cannot be used.    
++
+If you already have data in the AuraDB, a quick way to obtain Type Definitions is to use the https://graphql-toolbox.neo4j.io[Neo4j GraphQL Toolbox].  This facility has the ability to connect to an AuraDB, automatically create Type Definitions and allow GraphQL operations.  
++
+Alternatively you can write your own Type Definition from first principles by following the guidance provided in xref:index.adoc[Neo4j GraphQL Library] documention
++
+If you are using GraphQL Federation then make sure to select **Enable GraphQL subgraph**.
++
+image::aura-graphql/create/type-definitions.png[]
++
+. Cross-Origin Resource Sharing (CORS) policy
++
+If a browser based application will be using this GraphQL API, add an entry in your Cross-Origin Resource Sharing (CORS) policy.
+CORS is a browser-based security mechanism that prevents web pages from accessing resources from a server with a different origin.
+Allow the URL that serves the browser application by adding it to the CORS policy.
+This includes development environments such as node.js, which serves content on your localhost or similar.
+This also holds for using web-based tooling for GraphQL APIs such as https://studio.apollographql.com/[Apollo Studio].
++
+This is not needed if a non-browser-based application is using the GraphQL API as CORS does not apply to those.
+For example, if you are trying out GraphQL operations using cURL. 
++
+[NOTE]
+====
+The URL entered in the CORS policy must be an exact match.
+For example, http://localhost is not the same as http://localhost:3000/.
+Wildcards are not supported. 
+====
++
+To add a CORS policy entry, enter the exact URL, including HTTP/S and any port number, in the **Origin box**.
+If you need multiple entries, select **Add allowed origin**.
++
+image::aura-graphql/create/cors-policy.png[]
++
+. Authentication providers
++
+All requests to the GraphQL API are authenticated and there are two options for the type of authentication: API key or JSON Web Key Set (JWKS).
+It is possible to use these in combination and have multiples of each.   
++
+After choosing the authentication provider from the dropdown list, enter a friendly name.
+This is all that is needed when using API key.
+The API key will be shown after the GraphQL API key has been created.
+If you are using JWKS, provide a friendly name and the URL from your identity provider that is used to verify JWKS tokens. 
++
+Add more more providers via **Add authentication provider**.
++
+An authentication provider can be removed by selecting the trash icon.
++
+image::aura-graphql/create/auth-providers.png[]
++
+[CAUTION]
+====
+It is not recommended to use API keys with user-facing applications that are using the GraphQL API.
+This is due to the risk of the API key being visible to malicious users and very little control over GraphQL operations.
+A 3rd party identity provider with JWKS provides better security and allows for granular security rules, based on information within the JWKS token, to be defined within the type definitions to control GraphQL operations.
+====
++
+. Sizing
++
+Sizing a GraphQL API is based on the size and complexity of the type definitions and the workload that is serviced.
+Larger sizes have a higher hourly cost.
+If the cost is not displayed, refer to the agreement you have with Neo4j. 
++
+image::aura-graphql/create/sizing.png[]
++
+. Creation
++
+At this point the configuration is complete for the GraphQL API.
+Select **Create** to proceed and create the GraphQL API.
+Alternatively, **Cancel** the process at top right of the page.
++
+. API key
++
+If you chose to use an API key with the GraphQL API it is now displayed.
+Store this information securely as it cannot be retrieved again.
+Select **I understand** and then **Close** once you have done this.
++
+image::aura-graphql/create/save-api-key.png[]
++ 
+. The GraphQL API will now be provisioned.  
+You can see the status via **Data APIs** from the left side navigation.
+When the status changes to "Ready", the API is ready to use.
+If it has a status of 'Error', use the three dots icon and **Edit** from the menu to change the configuration.
+
+
+== Aura CLI
+
+Like the Console, the Aura CLI can also be used to create a GraphQL API.
+There is a difference: on creation, only an API Key authentication provider is created.
+The authentication providers can be modified using subsequent CLI commands.
+
+To create a GraphQL API with the Aura CLI, proceed as follows.
+
+. Find the AuraDB instance ID 
++
+From the table, locate the ID of the Aura instance that the GraphQL API will be used with.
++
+[source, bash, indent=0]
+----
+aura-cli instance list
+----
++
+. Save type definitions
++
+To avoid having to encode type definitions into base64 format to use directly with the Aura CLI, save them in a file.  
++
+. Create
++
+Provision the GraphQL API, replacing the values in UPPERCASE with your own:
++
+[source, bash, indent=0]
+----
+aura-cli data-api graphql create --name YOUR_FRIENDLY_NAME --instance-id YOUR_AURA_INSTANCE_ID --instance-username YOUR_AURA_INSTANCE_USER --instance-password YOUR_AURA_INSTANCE_PASSWORD --type-definitions-file FULL_PATH_TO_YOUR_TYPE_DEFS
+----
++
+The response shows information about the new GraphQL API.
+Make sure you note the API Key and ID.
++
+. Check progress
++ 
+To see if the GraphQL API is ready to use, run the following command:
++
+[source, bash, indent=0]
+----
+aura-cli data-api graphql get YOUR_GRAPHQL_API_ID --instance-id YOUR_AURA_INSTANCE_ID
+----
+
+If the status is "Ready", the API is ready to use.
+

modules/ROOT/pages/aura-graphql/api-deletion.adoc

@@ -0,0 +1,59 @@
+= Deleting a GraphQL API
+
+== Console
+
+. In Aura Console, select **Data API** from the left side navigation.
++
+. Locate the GraphQL API that you wish to delete and use the three dots icon, then **Delete**.
++
+Confirm the deletion by typing the name of the GraphQL API in the dialog and select **Delete** again. 
++
+image::aura-graphql/delete/confirm-deletion.png[]
+
+
+== Aura CLI
+
+Deletion of a GraphQL API using the Aura CLI requires:
+
+* The ID of the AuraDB the GraphQL API is being used with.
+* The ID of GraphQL API.
+
+[CAUTION]
+====
+The Aura CLI does not ask for confirmation and processes the command immediately.
+====
+
+
+=== Looking up the IDs
+
+. Find the ID of the AuraDB.
++ 
+Display a list of AuraDBs in a table:
++
+[source, bash, indent=0]
+----
+aura-cli instance list
+----
+From the table, find the AuraDB that has the GraphQL API that you wish to change.
+Make a note of its ID.
++
+. Find the GraphQL ID
++
+Using the AuraDB ID, list any GraphQL API that it may have:
++
+[source, bash, indent=0]
+----
+aura-cli data-api graphql list --instance-id YOUR_AURA_INSTANCE_ID
+----
++ 
+From that table, locate the GraphQL API you want to modify and make a note of its ID.
+
+
+=== Delete the GraphQL API  
+
+Using both the AuraDB instance ID and the ID of the associated GraphQL API, you can now delete the GraphQL API itself:
+
+[source, bash, indent=0]
+----
+aura-cli data-api graphql delete YOUR_GRAPHQL_DATA_API_ID  --instance-id YOUR_AURA_INSTANCE_ID
+----