bijection question

A question is a declared relation with closed arguments. Asking it reserves and saves one answer identity before any source work, then asks; read and control the answer with bijection answer.

Usage:
  bijection question [flags]
  bijection question [command]

Examples:
bijection question ask function:analytics:regionalSales --args '{"region":"west"}'
  bijection question ask collection:sales --relation '{"where":{"region":"west"},"select":["region","amount"]}'
  bijection question placements

Available Commands:
  ask         Ask a question or an ad-hoc relation over one collection
  explain     Explain one question or relation without asking it
  placements  Summarize where each declared question would run

Flags:
  -h, --help       help for question
      --help-all   Show all commands and options, including administrative controls.

Use "bijection question [command] --help" for more information about a command.

Reserve and save an answer identity, print it, then ask. If the reply is lost, rerun the same command with --answer-id: the identical request under the same identity never starts a second answer.

Usage:
  bijection question ask <question-or-collection> [flags]

Flags:
      --answer-id string    Retry an uncertain ask under its saved answer identity; keep the request unchanged.
      --args string         The question's declared arguments.
      --as string           Act as a person, such as alice, on a development, preview or local deployment. Production refuses development identities.
      --branch string       Use a branch under your current business identity.
      --deployment string   Inspect definitions in a specific deployment. Accepts:
                            • a deployment name (e.g. joyful-capybara-123)
                            • a deployment reference (e.g. dev/james, staging)
                            • dev (for your personal dev deployment)
                            • prod (for your project’s default production deployment).
                            You can also select deployments in other projects with project-slug:reference.
      --format string       Print the checked native answer state as JSON. (pretty, json) (default "pretty")
  -h, --help                help for ask
      --help-all            Show all commands and options, including administrative controls.
      --relation string     A bounded relation over the collection: where and select, or expressionJson, with optional max_rows and max_bytes.
      --url string          Inspect definitions in a private deployment at this explicit origin.

Plan the exact arguments under current access. Print the checked plan without reserving an answer or executing source work.

Usage:
  bijection question explain <question-or-collection> [flags]

Flags:
      --args string         The question's declared arguments.
      --as string           Act as a person, such as alice, on a development, preview or local deployment. Production refuses development identities.
      --branch string       Use a branch under your current business identity.
      --deployment string   Inspect definitions in a specific deployment. Accepts:
                            • a deployment name (e.g. joyful-capybara-123)
                            • a deployment reference (e.g. dev/james, staging)
                            • dev (for your personal dev deployment)
                            • prod (for your project’s default production deployment).
                            You can also select deployments in other projects with project-slug:reference.
      --format string       Output format; JSON preserves exact values. (pretty, json) (default "pretty")
  -h, --help                help for explain
      --help-all            Show all commands and options, including administrative controls.
      --relation string     An ad-hoc relation over one collection.
      --url string          Inspect definitions in a private deployment at this explicit origin.

Explain every declared question with placeholder arguments, one line each: its strategy, execution sites and the crossings it needs between them, or why no placement is admissible. Nothing executes and no data moves: planning reads source metadata only, and disclose rules are asked for advice. A question whose access depends on the caller or its arguments is decided when it is asked. Deploy cannot print this itself, since planning needs the installed sources' metadata.

Usage:
  bijection question placements [flags]

Flags:
      --deployment string   Explain the declared questions of a specific deployment. Accepts:
                            • a deployment name (e.g. joyful-capybara-123)
                            • a deployment reference (e.g. dev/james, staging)
                            • dev (for your personal dev deployment)
                            • prod (for your project’s default production deployment).
                            You can also select deployments in other projects with project-slug:reference.
  -h, --help                help for placements
      --help-all            Show all commands and options, including administrative controls.
      --url string          Explain the declared questions of a private deployment at this explicit origin.