tare gateway config init

Generate a starter gateway config file.

GCP (--type gcp, default):
  Provides the two minimum required values (serve domain + GCP project ID)
  via flags or, when stdin is a terminal, an interactive wizard. Other
  fields are derived from the serve domain (cert-map name, certificate
  name, DNS-authorization name, static-IP name, customer) or written as
  documented defaults (namespaces).

  Wizard prompt order: customer ID (required; matches the `customerId`
  field in your dataplane credential / identity.json), serve domain
  (required), GCP project ID (required), static IP name (optional —
  press Enter to skip; the same opt-out is available non-interactively
  via --static-ip-name="").

  Default output: gcp-gateway.json.

Azure (--type azure):
  Provides five required values (customer, serve domain, Azure subscription
  ID, resource group, AKS cluster name) via flags or the wizard. App Gateway
  name and subnet CIDR are written by the resolver at install time using
  documented defaults (<aks-cluster-name>-appgw and 10.225.0.0/24); they
  appear in the generator's "Generated values" provenance trail and can be
  edited directly in the output file.

  Default output: azure-gateway.json.

The generated file is designed to pass `tare gateway config lint --type <provider>`
cleanly out of the box. Edit the file directly to override any value.

Examples:
  # GCP wizard (interactive)
  tare gateway config init

  # GCP non-interactive
  tare gateway config init --serve-domain proxy.acme.tetrate.ai --project-id acme-prod

  # GCP explicit static IP / opt out of derived default
  tare gateway config init --static-ip-name acme-serve-ip
  tare gateway config init --static-ip-name=""

  # Azure wizard (interactive)
  tare gateway config init --type azure

  # Azure non-interactive
  tare gateway config init --type azure \
    --customer acme \
    --serve-domain proxy.acme.tetrate.test \
    --azure-subscription-id 00000000-0000-0000-0000-000000000000 \
    --azure-resource-group acme-aks-rg \
    --aks-cluster-name acme-aks

  # Custom output path / overwrite
  tare gateway config init --output ./gateway.json --force

Usage:
  tare gateway config init [flags]

Flags:
      --aks-cluster-name string        AKS cluster name (wizard prompts when empty)
      --azure-resource-group string    Azure resource group containing the AKS cluster (wizard prompts when empty)
      --azure-subscription-id string   Azure subscription ID (wizard prompts when --type azure and this is empty)
      --customer customerId            Customer ID — the customerId field at the top of your dataplane credential / service_account / identity.json. The wizard asks for this as the first required prompt; non-interactively, omit to fall back to a domain-derived slug.
      --force                          Overwrite the output file if it already exists
      --output string                  Output path (default: gcp-gateway.json or azure-gateway.json based on --type)
      --project-id string              GCP project ID; wizard prompts when empty
      --serve-domain string            Serve domain (e.g. proxy.acme.tetrate.ai); wizard prompts when empty
      --static-ip-name string          Static IP name (optional). Pass an empty value (--static-ip-name="") or press Enter at the wizard prompt to leave it empty in the output; omit the flag entirely to fall back to the slug-derived default.
      --type string                    Gateway provider type (gcp|azure; aws not implemented) (default "gcp")

Global Flags:
  -q, --quiet     Suppress progress output; only errors and the final summary go to stderr
  -v, --verbose   Verbose output: plain-mode progress lines plus full per-blob chunk logs to stderr