cortextool(1)

📦
version 0.21.1 · 2 versions
, in nixpkgs unstable

🦋 cortextool(1) — the little CLI that runs your Cortex life 💅

Okay bestie, settle in, because this is cortextool, from the General Commands Manual, and it's genuinely iconic. It's a whole command-line tool and it's here to help you manage cortex. That's it, that's the vibe. ✨

🌸 NAME 🌸

cortextool — yes, that's the name, that's the whole name, she's confident and she doesn't need a subtitle 😌

🎀 SYNOPSIS 🎀

cortextool [<flags>] <command> [<args> ...]

So it's flags first (optional), then a command (mandatory, main character energy), then whatever args that command wants. Simple. Slay.

💖 DESCRIPTION 💖

A command-line tool to manage cortex.

That's literally the whole description and honestly? Respect. She said "I do one thing and I do it well." 🫶

✨ OPTIONS ✨ (the global ones, the ones that go up top)

These are the big-picture flags, the ones that live before your command. Learn them once, use them everywhere. Obsessed.

  • --help — Show context-sensitive help. Also, lowkey, try --help-long and --help-man — she's got range 💅
  • --config="/homeless-shelter/.cortextool/config" — Path to the cortextool config file. Yes, that default path is real, yes it's giving "nobody's home," no we don't ask questions 🙈
  • --context=CONTEXT — Name of the context to use from the config file. Pick your fighter.
  • --log.level="info" — Sets the level of the logger. Default is "info", obviously.
  • --push-gateway.endpoint=PUSH-GATEWAY.ENDPOINT — The url for the push-gateway to register metrics. Drop that endpoint 🎯
  • --push-gateway.job=PUSH-GATEWAY.JOB — The job name to register metrics under.
  • --push-gateway.interval=1m — Interval to forward metrics to the push gateway. Default: 1m. Every minute, she checks in. Consistent queen. ⏰

👑 COMMANDS 👑

This is the good part. Buckle up, there's a lot and every single one matters. 💀

🧚 help [<command>...]

Show help. That's it. She's helpful, she's humble, she's the friend who actually reads the docs.

🔥 alerts verify [<flags>]

Verifies that alerts in an alertmanager cluster are deduplicated. Genuinely useful for verifying your configuration is correct when you're transferring from Prometheus to Cortex alert evaluation. Like a vibe check but for your alerts. 👀

  • --ignore-alerts=IGNORE-ALERTS — A comma separated list of Alert names to ignore in deduplication checks. Some alerts just get a pass, ok?
  • --source-label="prometheus" — Label to look for when deciding if two alerts are duplicates of eachother from separate sources. Default: "prometheus".
  • --grace-period=2 — Grace period. Don't consider alert groups with the incorrect amount of alert replicas erroneous unless the alerts have existed for more than this amount of time, in minutes. Default: 2.
  • --frequency=FREQUENCY — Setting this value will turn cortextool into a long-running process, running the alerts verify check every # of minutes specified. She'll just... keep going. Forever. No cap. 🔁

🌈 alertmanager get [<flags>]

Get the alertmanager config currently in the cortex alertmanager. Fetch, bestie.

  • --disable-color — disable colored output (sad, but sometimes you gotta, for the pipelines 😭)

⭐ alertmanager delete

Delete the alertmanager config currently in the cortex alertmanager.

Heads up: there's no flags listed for this one, no confirmer, no "are you sure" — just you, your choices, and the consequences 💀

🍓 alertmanager load <config> [<template-files>...]

load a set of rules to a designated cortex endpoint

Takes a <config> and then any number of [<template-files>...]. Load it up, she's carrying. 🫶

🦋 rules list [<flags>]

List the rules currently in the cortex ruler. Very "let me see what we're working with" of her.

  • --address=ADDRESS — Address of the cortex cluster, alternatively set CORTEX_ADDRESS or use config file.
  • --id=ID — Cortex tenant id, alternatively set CORTEX_TENANT_ID or use config file.
  • --use-legacy-routes — If set, API requests to cortex will use the legacy /api/prom/ routes, alternatively set CORTEX_USE_LEGACY_ROUTES.
  • --ruler-api-path="" — if set, API requests to cortex will use an alternative path for the ruler API, alternatively set CORTEX_RULER_API_PATH. The default is /api/v1/rules
  • --tls-ca-path="" — TLS CA certificate to verify cortex API as part of mTLS, alternatively set CORTEX_TLS_CA_PATH.
  • --tls-cert-path="" — TLS client certificate to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_CERT_PATH.
  • --tls-key-path="" — TLS client certificate private key to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_KEY_PATH.
  • --format=table — Backend type to interact with: <json|yaml|table>. Default: table.
  • --disable-color — disable colored output

💜 rules print [<flags>]

Print the rules currently in the cortex ruler. Same energy as list but make it print. 🖨️

  • --address=ADDRESS — Address of the cortex cluster, alternatively set CORTEX_ADDRESS or use config file.
  • --id=ID — Cortex tenant id, alternatively set CORTEX_TENANT_ID or use config file.
  • --use-legacy-routes — If set, API requests to cortex will use the legacy /api/prom/ routes, alternatively set CORTEX_USE_LEGACY_ROUTES.
  • --ruler-api-path="" — if set, API requests to cortex will use an alternative path for the ruler API, alternatively set CORTEX_RULER_API_PATH. The default is /api/v1/rules
  • --tls-ca-path="" — TLS CA certificate to verify cortex API as part of mTLS, alternatively set CORTEX_TLS_CA_PATH.
  • --tls-cert-path="" — TLS client certificate to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_CERT_PATH.
  • --tls-key-path="" — TLS client certificate private key to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_KEY_PATH.
  • --disable-color — disable colored output

🎯 rules get [<flags>] <namespace> <group>

Retrieve a rulegroup from the ruler. You give her a namespace and a group, she gives you the goods. 💅

  • --address=ADDRESS — Address of the cortex cluster, alternatively set CORTEX_ADDRESS or use config file.
  • --id=ID — Cortex tenant id, alternatively set CORTEX_TENANT_ID or use config file.
  • --use-legacy-routes — If set, API requests to cortex will use the legacy /api/prom/ routes, alternatively set CORTEX_USE_LEGACY_ROUTES.
  • --ruler-api-path="" — if set, API requests to cortex will use an alternative path for the ruler API, alternatively set CORTEX_RULER_API_PATH. The default is /api/v1/rules
  • --tls-ca-path="" — TLS CA certificate to verify cortex API as part of mTLS, alternatively set CORTEX_TLS_CA_PATH.
  • --tls-cert-path="" — TLS client certificate to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_CERT_PATH.
  • --tls-key-path="" — TLS client certificate private key to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_KEY_PATH.
  • --disable-color — disable colored output

💀 rules delete [<flags>] <namespace> <group>

Delete a rulegroup from the ruler. Gone. Poof. She's not asking twice (well, actually, she's not asking at all 🙈).

  • --address=ADDRESS — Address of the cortex cluster, alternatively set CORTEX_ADDRESS or use config file.
  • --id=ID — Cortex tenant id, alternatively set CORTEX_TENANT_ID or use config file.
  • --use-legacy-routes — If set, API requests to cortex will use the legacy /api/prom/ routes, alternatively set CORTEX_USE_LEGACY_ROUTES.
  • --ruler-api-path="" — if set, API requests to cortex will use an alternative path for the ruler API, alternatively set CORTEX_RULER_API_PATH. The default is /api/v1/rules
  • --tls-ca-path="" — TLS CA certificate to verify cortex API as part of mTLS, alternatively set CORTEX_TLS_CA_PATH.
  • --tls-cert-path="" — TLS client certificate to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_CERT_PATH.
  • --tls-key-path="" — TLS client certificate private key to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_KEY_PATH.

🌸 rules delete-namespace [<flags>] <namespace>

Delete a namespace from the ruler. Whole namespace. The way she just takes it ALL out 😭

  • --address=ADDRESS — Address of the cortex cluster, alternatively set CORTEX_ADDRESS or use config file.
  • --id=ID — Cortex tenant id, alternatively set CORTEX_TENANT_ID or use config file.
  • --use-legacy-routes — If set, API requests to cortex will use the legacy /api/prom/ routes, alternatively set CORTEX_USE_LEGACY_ROUTES.
  • --ruler-api-path="" — if set, API requests to cortex will use an alternative path for the ruler API, alternatively set CORTEX_RULER_API_PATH. The default is /api/v1/rules
  • --tls-ca-path="" — TLS CA certificate to verify cortex API as part of mTLS, alternatively set CORTEX_TLS_CA_PATH.
  • --tls-cert-path="" — TLS client certificate to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_CERT_PATH.
  • --tls-key-path="" — TLS client certificate private key to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_KEY_PATH.

🌟 rules load [<flags>] <rule-files>...

load a set of rules to a designated cortex endpoint

Give her one or more <rule-files> and she'll ship them. 🚀

  • --address=ADDRESS — Address of the cortex cluster, alternatively set CORTEX_ADDRESS or use config file.
  • --id=ID — Cortex tenant id, alternatively set CORTEX_TENANT_ID or use config file.
  • --use-legacy-routes — If set, API requests to cortex will use the legacy /api/prom/ routes, alternatively set CORTEX_USE_LEGACY_ROUTES.
  • --ruler-api-path="" — if set, API requests to cortex will use an alternative path for the ruler API, alternatively set CORTEX_RULER_API_PATH. The default is /api/v1/rules
  • --tls-ca-path="" — TLS CA certificate to verify cortex API as part of mTLS, alternatively set CORTEX_TLS_CA_PATH.
  • --tls-cert-path="" — TLS client certificate to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_CERT_PATH.
  • --tls-key-path="" — TLS client certificate private key to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_KEY_PATH.

🧚 rules diff [<flags>] [<rule-files>...]

diff a set of rules to a designated cortex endpoint

She compares. She reports. She does NOT let you push blind. This is the responsible friend of the group and we love her for it. 💖

  • --address=ADDRESS — Address of the cortex cluster, alternatively set CORTEX_ADDRESS or use config file.
  • --id=ID — Cortex tenant id, alternatively set CORTEX_TENANT_ID or use config file.
  • --use-legacy-routes — If set, API requests to cortex will use the legacy /api/prom/ routes, alternatively set CORTEX_USE_LEGACY_ROUTES.
  • --ruler-api-path="" — if set, API requests to cortex will use an alternative path for the ruler API, alternatively set CORTEX_RULER_API_PATH. The default is /api/v1/rules
  • --tls-ca-path="" — TLS CA certificate to verify cortex API as part of mTLS, alternatively set CORTEX_TLS_CA_PATH.
  • --tls-cert-path="" — TLS client certificate to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_CERT_PATH.
  • --tls-key-path="" — TLS client certificate private key to authenticate with cortex API as part of mTLS, alternatively set CORTEX_TLS_KEY_PATH.
  • --namespaces=NAMESPACES — comma-separated list of namespaces to check during a diff. Cannot be used together with --ignored-namespaces.
  • --ignored-namespaces=IGNORED-NAMESPACES — comma-separated list of namespaces to ignore during a diff. Cannot be used together with --namespaces.
  • --rule-files=RULE-FILES — The rule files to check. Flag can be reused to load multiple files. Reuse it, she doesn't mind 🫶
  • --rule-dirs=RULE-DIRS — Comma separated list of paths to directories containing rules yaml files. Each file in a directory with a .yml or .yaml suffix will be parsed.
  • --disable-color — disable colored output
  • --verbose — show diff output with rules changes
Two things to keep in your cute little head: --namespaces and --ignored-namespaces can NOT be used together, and that's not a suggestion, that's a rule 🚫

and that's literally just part one bestie, she's still going — 💅

🌸 rules sync — push your rules to Cortex

rules sync [<flags>] [<rule-files>...]

okay so this one syncs a whole set of rules to a designated cortex endpoint. bestie, it's the ✨ main character ✨ of the rules workflow imo.

  • --address=ADDRESS — the address of the cortex cluster. you can also set CORTEX_ADDRESS instead, or just use the config file 💖
  • --id=ID — your Cortex tenant id. alternatively set CORTEX_TENANT_ID, or use the config file 🫶
  • --use-legacy-routes — if set, API requests to cortex will use the legacy /api/prom/ routes. alternatively set CORTEX_USE_LEGACY_ROUTES 🦋
  • --ruler-api-path="" — if set, API requests to cortex will use an alternative path for the ruler API, alternatively set CORTEX_RULER_API_PATH. the default is /api/v1/rules 👑
  • --tls-ca-path="" — TLS CA certificate to verify the cortex API as part of mTLS, alternatively set CORTEX_TLS_CA_PATH 🔐
  • --tls-cert-path="" — TLS client certificate to authenticate with the cortex API as part of mTLS, alternatively set CORTEX_TLS_CERT_PATH 🔐
  • --tls-key-path="" — TLS client certificate private key to authenticate with the cortex API as part of mTLS, alternatively set CORTEX_TLS_KEY_PATH 🔑
  • --namespaces=NAMESPACES — comma-separated list of namespaces to check during a diff. cannot be used together with --ignored-namespaces 🚫
  • --ignored-namespaces=IGNORED-NAMESPACES — comma-separated list of namespaces to ignore during a sync. cannot be used together with --namespaces 🚫
  • --rule-files=RULE-FILES — the rule files to check. the flag can be reused to load multiple files 📚
  • --rule-dirs=RULE-DIRS — comma separated list of paths to directories containing rules yaml files. every file in a directory with a .yml or .yaml suffix will be parsed ✨
lowkey important: --namespaces and --ignored-namespaces are giving sworn enemies — pick one, you literally cannot have both 💀

🎀 rules prepare — glow-up your aggregations

rules prepare [<flags>] [<rule-files>...]

this one modifies a set of rules by including a specific label in aggregations. it's giving "let me just add a little something" 💅

  • --rule-files=RULE-FILES — the rule files to check. flag can be reused to load multiple files 📚
  • --rule-dirs=RULE-DIRS — comma separated list of paths to directories containing rules yaml files. every file in a directory with a .yml or .yaml suffix will be parsed ✨
  • -i, --in-place — edits the rule file in place. (yes bestie it's literally editing your files, so maybe peek at them first 🙈)
  • -l, --label="cluster" — the label to include as part of the aggregations. default is "cluster" 🏷️
  • --label-excluded-rule-groups=LABEL-EXCLUDED-RULE-GROUPS — comma separated list of rule group names to exclude when including the configured label to aggregations 🙅‍♀️

🦋 rules lint — the formatting fairy

rules lint [<flags>] [<rule-files>...]

formats a set of rule files. it reorders keys alphabetically, uses 4 spaces as indentantion, and formats PromQL expressions to a single line. so satisfying, ngl 😌✨

  • --rule-files=RULE-FILES — the rule files to check. flag can be reused to load multiple files 📚
  • --rule-dirs=RULE-DIRS — comma separated list of paths to directories containing rules yaml files. every file in a directory with a .yml or .yaml suffix will be parsed ✨
  • -n, --dry-run — performs a trial run that doesn't make any changes and (mostly) produces the same outpupt as a real run 👀

🔥 rules check — bestie behaviour enforcement

rules check [<flags>] [<rule-files>...]

runs various best practice checks against rules. it's the friend who tells you your outfit is cute but your shoes don't match 🫶

  • --rule-files=RULE-FILES — the rule files to check. flag can be reused to load multiple files 📚
  • --rule-dirs=RULE-DIRS — comma separated list of paths to directories containing rules yaml files. every file in a directory with a .yml or .yaml suffix will be parsed ✨
  • --strict — fails rules checks that do not match best practices exactly. no notes, no grace, no vibes 💀

⭐ loadgen — the stress-test queen

loadgen [<flags>]

simple load generator for Cortex. she generates. she loads. she serves metrics 💅

  • --write-url="" — the write URL 🌐
  • --series-name="node_cpu_seconds_total" — name of the metric that will be generated ✨
  • --active-series=1000 — number of active series to send 🔢
  • --scrape-interval=15s — period to send metrics ⏰
  • --parallelism=10 — how many metrics to send simultaneously 🏃‍♀️
  • --batch-size=100 — how big a batch to send 📦
  • --write-timeout=500ms — timeout for write requests ⏳
  • --query-url="" — the query URL 🔍
  • --query="sum(node_cpu_seconds_total)" — query to run 🧮
  • --query-parallelism=10 — number of queries to run in parallel ⚡
  • --query-timeout=20s — timeout for queries ⏳
  • --query-duration=1h — length of query 🕐
  • --metrics-listen-address=":8080" — address to serve metrics on 📡

💜 remote-read export — take your metrics home

remote-read export --address=ADDRESS [<flags>]

export metrics remote read series into a local TSDB. it's giving "packing up your stuff and moving out" 📦✨

  • --address=ADDRESS — address of the cortex cluster, alternatively set $CORTEX_ADDRESS 💖
  • --remote-read-path="/prometheus/api/v1/read" — path of the remote read endpoint 🛣️
  • --id="" — Cortex tenant id, alternatively set $CORTEX_TENANT_ID 🫶
  • --key="" — api key to use when contacting cortex, alternatively set $CORTEX_API_KEY 🔑
  • --read-timeout=30s — timeout for read requests ⏳
  • --selector="up" — PromQL selector to filter metrics on. to return all metrics, '{__name__!=""}' can be used 🎯
  • --from="2026-10-21T20:15:19Z" — start of the time window to select metrics 📅
  • --to="2026-10-21T21:15:19Z" — end of the time window to select metrics 📅
  • --tsdb-path="" — path to the folder where to store the TSDB blocks, if not set a new directory in $TEMP is created 🗂️

🌈 remote-read dump — spill the tea

remote-read dump --address=ADDRESS [<flags>]

dump remote read series. literally just dumping them out, no filter, no shame 🫗

  • --address=ADDRESS — address of the cortex cluster, alternatively set $CORTEX_ADDRESS 💖
  • --remote-read-path="/prometheus/api/v1/read" — path of the remote read endpoint 🛣️
  • --id="" — Cortex tenant id, alternatively set $CORTEX_TENANT_ID 🫶
  • --key="" — api key to use when contacting cortex, alternatively set $CORTEX_API_KEY 🔑
  • --read-timeout=30s — timeout for read requests ⏳
  • --selector="up" — PromQL selector to filter metrics on. to return all metrics, '{__name__!=""}' can be used 🎯
  • --from="2026-10-21T20:15:19Z" — start of the time window to select metrics 📅
  • --to="2026-10-21T21:15:19Z" — end of the time window to select metrics 📅

🍓 remote-read stats — the numbers version

remote-read stats --address=ADDRESS [<flags>]

show statistic of remote read series. the way that this just gives you the receipts 😭📊

  • --address=ADDRESS — address of the cortex cluster, alternatively set $CORTEX_ADDRESS 💖
  • --remote-read-path="/prometheus/api/v1/read" — path of the remote read endpoint 🛣️
  • --id="" — Cortex tenant id, alternatively set $CORTEX_TENANT_ID 🫶
  • --key="" — api key to use when contacting cortex, alternatively set $CORTEX_API_KEY 🔑
  • --read-timeout=30s — timeout for read requests ⏳
  • --selector="up" — PromQL selector to filter metrics on. to return all metrics, '{__name__!=""}' can be used 🎯
  • --from="2026-10-21T20:15:19Z" — start of the time window to select metrics 📅
  • --to="2026-10-21T21:15:19Z" — end of the time window to select metrics 📅

🧚 acl generate-header — the golden ticket

acl generate-header --id=ID --rule=RULE

generate the header that needs to be passed to the datasource for setting ACLs. it's giving backstage pass 🎫✨

  • --id=ID — Cortex tenant ID, alternatively set CORTEX_TENANT_ID 🫶
  • --rule=RULE — the access control rules (Prometheus selectors). set it multiple times to set multiple rules 🔁

💖 analyse prometheus — cardinality detective era

analyse prometheus --address=ADDRESS [<flags>]

take the metrics being used in Grafana and get the cardinality from a Prometheus. she investigates 🔍💅

  • --address=ADDRESS — address of the Prometheus/Cortex instance, alternatively set $CORTEX_ADDRESS 💖
  • --id="" — username to use when contacting Prometheus/Cortex, alternatively set $CORTEX_TENANT_ID 🫶
  • --key="" — password to use when contacting Prometheus/Cortex, alternatively set $CORTEX_API_KEY 🔑
  • --read-timeout=30s — timeout for read requests ⏳
  • --grafana-metrics-file="metrics-in-grafana.json" — the path for the input file containing the metrics from the grafana-analyse command 📄
  • --ruler-metrics-file="metrics-in-ruler.json" — the path for the input file containing the metrics from the ruler-analyse command 📄
  • --output="prometheus-metrics.json" — the path for the output file 📤

🌸 analyse grafana — dashboard archaeology

analyse grafana --address=ADDRESS [<flags>]

analyse and output the metrics used in Grafana Dashboards. bestie we are going digging through dashboards 🔎

  • --address=ADDRESS — address of the Grafana instance, alternatively set $GRAFANA_ADDRESS 💖
  • --key="" — api key to use when contacting Grafana, alternatively set $GRAFANA_API_KEY 🔑
  • --read-timeout=300s — timeout for read requests ⏳
  • --output="metrics-in-grafana.json" — the path for the output file 📤

🎀 analyse ruler — rules, but make it metrics

analyse ruler --address=ADDRESS [<flags>]

analyse and extract the metrics used in Cortex rules 🧠✨

  • --address=ADDRESS — address of the Prometheus/Cortex instance, alternatively set $CORTEX_ADDRESS 💖
  • --id="" — username to use when contacting Prometheus/Cortex, alternatively set $CORTEX_TENANT_ID 🫶
  • --key="" — password to use when contacting Prometheus/Cortex, alternatively set $CORTEX_API_KEY 🔑
  • --output="metrics-in-ruler.json" — the path for the output file 📤

🦋 analyse dashboard — feeding it files

analyse dashboard [<flags>] <files>...

analyse and output the metrics used in Grafana dashboard files. you literally hand her the files, she does the rest 💁‍♀️

  • --output="metrics-in-grafana.json" — the path for the output file 📤

💜 analyse rule-file — same energy, rules version

analyse rule-file [<flags>] <files>...

analyse and output the metrics used in Prometheus rules files 📜✨

  • --output="metrics-in-ruler.json" — the path for the output file 📤

👑 bucket-validation — trust but verify

bucket-validation [<flags>]

validate that an object store bucket works correctly. she does a little vibe check on your bucket 🪣✅

  • --object-count=2000 — number of objects to create & delete 🔢
  • --report-every=100 — every X operations a progress report gets printed 📈
  • --test-runs=1 — number of times we want to run the whole test 🔁
  • --prefix="tenant" — path prefix to use for test objects in object store 🏷️
  • --retries-on-error=3 — number of times we want to retry if object store returns error 🔄
  • --bucket-config=BUCKET-CONFIG — the CLI args to configure a storage bucket 🪣
  • --bucket-config-help — help text explaining how to use the -bucket-config parameter 🆘

⭐ config view — see the whole picture

config view

display merged configuration. everything, all at once, merged 🫶

🌈 config get-contexts — roll call

config get-contexts

list all contexts 📋

🍓 config current-context — where are we rn

config current-context

display the current context 📍

🧚 config use-context — switch it up

config use-context <name>

set the current context ✨

🎀 config set-context — build the vibe

config set-context [<flags>] <name>

create or modify a context 🛠️

  • --cluster=CLUSTER — cluster name for the context 🏢
  • --user=USER — user name for the context 👤

💖 config set-cluster — cluster era

config set-cluster [<flags>] <name>

create or modify a cluster 🌐

  • --address=ADDRESS — Cortex cluster address 📍
  • --tls-ca-path=TLS-CA-PATH — TLS CA certificate path 🔐
  • --tls-cert-path=TLS-CERT-PATH — where your TLS client certificate lives, bestie. drop the path and she's ready to show her ID 💳
  • --tls-key-path=TLS-KEY-PATH — and this is the matching TLS client key path. they're a set, don't separate them 😭
  • --use-legacy-routes — flips you over to the legacy API routes. old school, but sometimes old school is the vibe 🫶
  • --ruler-api-path=RULER-API-PATH — wanna point at a custom ruler API path? say less, that's literally this flag ✨

🎀 config set-credentials [<flags>] <name>

okay so this one is the moment you create or modify user credentials — yes, both, it's giving multitasking main character energy 👑

  • --id=ID — the Tenant ID. know your tenant, love your tenant 🏠
  • --user=USER — your Basic auth username. iconic, essential 🪪
  • --key=KEY — the Basic auth password/key that goes with it. guard it with your life, no cap 🔐
  • --auth-token=AUTH-TOKEN — a Bearer token for JWT auth. different auth flavor, same slay 💅

🦋 config delete-context <name>

Deletes a context. that's it, that's the whole thing — poof, gone, she's not coming back 🙈

⭐ version

Gets the version of the cortextool CLI. tiny command, big "is my stuff up to date" energy 🧚

and that's the whole page, bestie — you made it to the end, I'm so proud 😭💖

this was cortextool(1) — that's the footer, and yeah, I'm mentioning it in the sign-off because we're cute like that 🎀 go forth and run your commands, you gorgeous nerd 👑✨
📦 where this page comes from