Initial data api docs

Author: Liam-Doodson

modules/ROOT/content-nav.adoc

@@ -58,6 +58,11 @@
 
 * *Products*
 
+* xref:aura-graphql-data-apis/index.adoc[]
+** xref:aura-graphql-data-apis/prerequisites.adoc[]
+** xref:aura-graphql-data-apis/deploy-and-operate.adoc[]
+** xref:aura-graphql-data-apis/authentication-providers.adoc[]
+
 * xref:introspector.adoc[Introspector]
 
 * *Frameworks and integrations*

modules/ROOT/images/aura-graphql-data-apis/console-classic-api-keys.png

@@ -0,0 +1,2 @@
+[[auth-providers]]
+= Authentication Providers

modules/ROOT/images/aura-graphql-data-apis/console-classic-home.png

@@ -0,0 +1,73 @@
+= Deploy and Operate
+
+== Deploy a GraphQL Data API
+
+
+Deploying a GraphQL Data API requires you first to have completed the steps in xref::/aura-graphql-data-apis/prerequisites.adoc[Prerequisites]. Of particular importance is that you have:
+
+* The ID, username and password for the AuraDB
+* A file containing the type definitions
+
+You are now ready to create the GraphQL Data API with the Aura CLI. Substitute the values in `CAPITALS` to match your setup:
+
+[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 --await
+----
+
+[NOTE]
+====
+Make sure to record the API key shown in the response as it will not be displayed again. If the API key is lost, a new one can be created by following the steps to create a new API key auth provider in the xref::/aura-graphql-data-apis/authentication-providers.adoc[authentication provider] section
+====
+
+There are other items of note in the response:
+
+* `id`: unique identifier for the GraphQL Data API
+* `status`: tells you if the GraphQL Data API is ready to receive requests
+* `url`: the connection address to access the Data API
+
+To check if the GraphQL Data API is ready for requests, use the Aura CLI again, changing `YOUR-AURA-INSTANCE-ID` for the ID of your aura instance.
+
+[source, bash, indent=0]
+----
+aura-cli data-api graphql list --instance-id YOUR-AURA-INSTANCE-ID
+----
+
+When the status changes to `ready`, the GraphQL Data API is available for servicing requests.
+
+== Modifying an Existing GraphQL Data API
+
+It is possible to change the configuration of an existing GraphQL Data API. The following properties can be modified:
+
+* Friendly name of the GraphQL Data API
+* Username and/or password for the associated Aura instance
+* Type definitions
+
+To do this, use the Aura CLI update command which requires IDs of the GraphQL Data API and it’s linked AuraDB instance. The format of this Aura CLI command is as follows:
+
+[source, bash, indent=0]
+----
+aura-cli data-api graphql update YOUR-DATA-API-ID --instance-id YOUR-AURA-INSTANCE-ID <flags>
+----
+
+As the change takes a few moments to fully implement, you should check the status of the GraphQL Data API after performing this operation; if the status is `updating` then the change is still being processed. When the change is committed, the status will return to `ready`.
+
+
+Additionally, it is possible to modify the authentication providers of a GraphQL Data APIs. More on what these are and how to do this xref::/aura-graphql-data-apis/authentication-providers.adoc[here].
+
+== Deleting a GraphQL Data API
+
+When you no longer require the GraphQL Data API then delete it by using the Aura CLI delete command. This will require the Aura instance ID and ID of the GraphQL Data API.
+
+The format of this command is as follows:
+
+[source, bash, indent=0]
+----
+aura-cli data-api graphql delete YOUR-DATA-API-ID --instance-id YOUR-AURA-INSTANCE-ID
+----
+
+[NOTE]
+====
+There is no additional confirmation - the GraphQL Data API will start to be deleted as soon as you press the Enter key!
+====

modules/ROOT/images/aura-graphql-data-apis/unified-console-account-dropdown.png

@@ -0,0 +1,23 @@
+= GraphQL for Neo4j AuraDB Beta
+
+== Foreword
+
+Welcome to the beta release of *GraphQL Data APIs for Neo4j AuraDB*.
+
+We are thrilled to have you join us at this exciting stage of our journey. Participating is more than just trying out this feature – your feedback and insights will directly influence how we refine and evolve its future to meet the needs of users like you.
+
+This beta release is designed to give you a first look at *GraphQL Data APIs for Neo4j AuraDB*. While we’ve worked hard to ensure a functional and valuable experience, there is the chance that you may encounter suboptimal behavior. We see these occasions as chances to listen, learn, and improve before *GraphQL for Neo4j AuraDB* is released to all of our customers.
+
+Here’s how you can help us get *GraphQL Data APIs for Neo4j AuraDB* ready for production:
+
+- *Dive in*: Explore and test its features to your heart’s content.
+- *Break stuff*: We’d rather discover weak areas at this stage – go for it, don’t hold back.
+- *Share your experience*: Tell us what works, what doesn’t, and what you’d like to see in the future.
+- *Stay in touch*: Use email (`[email protected]`), our `#graphal` channel on our https://discord.gg/M8mTADEJ[Discord Community], or our https://community.neo4j.com/c/drivers-stacks/graphql/33[forums] to report issues, suggest improvements, or ask questions.
+
+We value your time, creativity, and honest feedback – thank you for your trust and collaboration.
+
+Sincerely,
+
+Jonathan Giffard
+The GraphQL Team at Neo4j