Get the JSON schema that defines how to create a valid neptune.json file.

IMPORTANT: Use this tool BEFORE creating or modifying 'neptune.json' to ensure the configuration is valid.

This schema defines the exact structure and constraints for neptune.json files:

• Required fields (kind, name)

• Optional fields (resources, port_mappings, cpu, memory)

• Valid resource types (StorageBucket, Secret) and their properties

• Allowed values for each field

The returned schema is a standard JSON Schema that you should use as the authoritative reference when generating neptune.json configurations.

Authenticate with Neptune.

Opens a browser window for OAuth login. After successful authentication, the access token is saved for use with Neptune tools.

Get information about resource types that can be provisioned on Neptune.

IMPORTANT: Always use this tool before modifying 'neptune.json'. This is to ensure your modification is correct.

Valid 'kind' are: "StorageBucket" and "Secret".

Provision necessary cloud resources for the current project as per its configuration

If the working directory does not contain a 'neptune.json' file, an error message is returned.

Delete a project and all its resources.

WARNING: This permanently deletes the project and all associated resources including storage buckets and secrets. This action cannot be undone.

Deploy the current project.

This only works after the project has been provisioned using 'provision_resources'.

UNDER THE HOOD: this tool builds an image using the Dockerfile in the current directory.

Note: running tasks are not persistent; if the task stops or is redeployed, all data stored in the container is lost. Use provisioned resources (storage buckets, etc.) for persistent data storage.

Get the status of the current deployment of a project and its provisioned resources.

This will tell you about running resources the project is using, as well as the state of the service.

Set the value of a secret resource for the current project.

This will elicit a prompt to securely enter the secret value.

Note the secret must already exist in the neptune.json configuration of the project. It must also be provisioned using 'provision_resources' before setting its value.

List all files in a storage bucket resource for the current project.

Note the bucket must already exist in the neptune.json configuration of the project. It must also be provisioned using 'provision_resources' before listing its files.

Retrieve an object from a storage bucket resource for the current project.

Note the bucket must already exist in the neptune.json configuration of the project. It must also be provisioned using 'provision_resources' before retrieving its objects.

Wait for the current project deployment to complete.

Retrieve the logs for the current project deployment.

Get information about Neptune and available tools for cloud deployment management.

List all projects in the current account.

Query a database resource for the current project. This will return the results of the query as a dictionary. You can use the 'where_clause' parameter to filter the results of the query. Example:

query_database(neptune_json_path, "users", "age > 18")

This will return the results of the query as a dictionary. You can use the 'table_name' parameter to specify the table to query. Example:

query_database(neptune_json_path, "users", "age > 18")

Note the database must already exist in the neptune.json configuration of the project. It must also be provisioned using 'provision_resources' before querying it.