my613-cli v0.1.0

my613-cli

CLI interface for My613

npm install -g my613-cli
my613 login
my613 schema-fetch

Usage

my613 login [url] [token]

Login to My613 using given My613 URL and token. Prompts for url and token if they are not provided. Credentials are stored in .netrc file in user's HOME folder.

my613 logout

Clear stored credentials.

my613 graphiql

Opens GraphiQL console for your app in your browser.

my613 schema-fetch [SCHEMA_FILE] [--force]

Fetch My613 JSON schema to SCHEMA_FILE file (My613Schema.json if not provided).

If --force flag is not set, it will not run if schema file already exists.

my613 schema-push [SCHEMA_FILE] [--dry-run --force]

Push JSON schema from SCHEMA_FILE (defaults to My613Schema.json) to My613 API to perform a migration. Validates the schema and runs the migration, if it only includes safe operations.

If the migration includes destructive operations, --force flag must be used to run it.

If --dry-run flag is given, the command only validates the schema and displays the migration without running.

my613 schema-relay OUTPUT

Get Relay compatible GraphQL schema from My613 API at HOST. OUTPUT is a file name. If output is specified, result is written into it. Otherwise result is written to stdout.

Options

-u MY613_URL --url MY613_URL

Your My613 application host (eg https://YOURAPP.my613.com). Can be set either with this flag or via MY613_URL environment variable. If you use my613 login, this parameter overrides stored credentials.

-t MY613_TOKEN --token MY613_TOKEN

Your My613 application authorization token. Can be set either with this flag or via MY613_TOKEN environment variable. If you use my613 login, this parameter overrides stored credentials.