devnomads-cli 0.9.1__tar.gz → 0.11.0__tar.gz

{devnomads_cli-0.9.1 → devnomads_cli-0.11.0}/PKG-INFO

@@ -1,17 +1,17 @@
 Metadata-Version: 2.4
 Name: devnomads-cli
-Version: 0.9.1
+Version: 0.11.0
 Summary: Manage your DevNomads services from the command line
 Author-email: DevNomads <support@devnomads.nl>
 License: MIT
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: typer>=0.12
+Requires-Dist: typer>=0.19
 Requires-Dist: httpx>=0.27
 Requires-Dist: rich>=13
 Requires-Dist: cryptography>=42
-Requires-Dist: devnomads[acme]>=0.5.0
+Requires-Dist: devnomads[acme]>=0.6.0
 Dynamic: license-file
 
 # dncli
@@ -26,18 +26,43 @@ as **`devnomads-cli`**.
 
 ## Install
 
+Install dncli with [uv](https://docs.astral.sh/uv/). It gives dncli
+its own isolated environment and puts the `dncli` command on your
+PATH:
+
 ```sh
-pip install devnomads-cli
+uv tool install devnomads-cli
 ```
 
-For a global, isolated install (recommended on workstations), use
-[uv](https://docs.astral.sh/uv/) or pipx instead - same result, no
-interference with system packages:
+No uv yet? Install it first:
+
+```sh
+curl -LsSf https://astral.sh/uv/install.sh | sh                               # macOS, Linux
+powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"  # Windows
+```
+
+pipx (`pipx install devnomads-cli`) and pip (`pip install
+devnomads-cli`) work as well.
+
+### Updates
+
+Update with:
 
 ```sh
-uv tool install devnomads-cli   # or: pipx install devnomads-cli
+uv tool upgrade devnomads-cli
 ```
 
+dncli checks PyPI at most once a day and tells you when a new version
+is out, with the command to update the way you installed it. It only
+does so on an interactive terminal, never in pipes, scripts or CI; set
+`DN_NO_UPDATE_CHECK=1` to turn it off.
+
+dncli also warns when the DevNomads API reports a major version it was
+not built for, and tells you when the API no longer supports your
+dncli version. Update dncli in both cases.
+
+### Shell completion
+
 Enable shell completion (bash, zsh, fish, PowerShell):
 
 ```sh
@@ -65,7 +90,8 @@ dncli containers show <id>
 
 Every DevNomads product has its own command group - `apps`,
 `buckets`, `containers`, `databases`, `domains`, `emails`,
-`forwards`, `proxies`, `servers`, `sites` and more. Explore with
+`forwards`, `proxies`, `servers`, `sites` and more, plus `keys` for
+your SSH keys and `jobs` for background work. Explore with
 `dncli --help` and `dncli <group> --help`.
 
 Commands accept any unambiguous prefix: `dncli e l` is `dncli emails
@@ -81,6 +107,18 @@ dncli dns records set example.com www A 192.0.2.1 --ttl 3600
 dncli dns records delete example.com www A
 ```
 
+Anywhere a zone is expected you may pass the service id of a domain
+instead of its name, so the ids from `dncli domains list` work here
+too:
+
+```sh
+dncli dns records list 42
+```
+
+An id always means that domain's own zone. A delegated subzone such
+as `foo.example.com` has no domain service of its own, so address it
+by name.
+
 ## Moving a zone from another provider
 
 `dncli dns transfer` copies a zone from your current DNS provider
@@ -108,6 +146,17 @@ dncli services list --profile acme
 export DN_PROFILE=acme
 ```
 
+Manage stored profiles:
+
+```sh
+dncli configure list                 # profiles, with keys masked
+dncli configure set-key acme         # replace a profile's API key
+dncli configure delete acme          # remove a profile
+```
+
+`set-key --stdin` reads the new key from standard input, and
+`delete --yes` skips the question, for use in scripts.
+
 ## Scripting
 
 Output is a human-readable table on a terminal and JSON when piped,
@@ -131,9 +180,23 @@ fields, and reports an error on an unknown column name.
 
 Commands that take a service id also accept a unique entity name and
 resolve it for you, so `dncli domains show example.com` works as well
-as `dncli domains show 1234`. A purely numeric value is always treated
-as an id; an entity that matches more than one service is rejected, so
-pass the id when an entity is not unique.
+as `dncli domains show 1234`. Names match regardless of case. A purely
+numeric value is always treated as an id; an entity that matches more
+than one service is rejected, so pass the id when an entity is not
+unique. Other references, such as cluster, key or user ids, take the
+numeric id only.
+
+Some changes run in the background: creating a site, server, proxy or
+domain, for example, queues one or more jobs in a batch. Such a command
+prints the queued jobs and returns right away; add `--wait` to follow
+the batch until every job has finished and see how each one ended.
+With `--wait` the exit status is 0 only when every job completed. You
+can look a batch up later with `dncli jobs batches show <batch_id>`.
+
+The exit status is 0 when the API accepted the request and 1 for any
+error response, so `dncli ... && next-step` is safe in scripts. Every
+command takes `--timeout <seconds>` (default 300) for how long to wait
+for the API, including the time spent waiting on `--wait`.
 
 In CI and pipelines, skip the credentials file and pass the key via
 the environment:
@@ -143,6 +206,22 @@ export DN_API_KEY=...        # beats any stored profile
 dncli services list | jq -r '.[].entity'
 ```
 
+## AI agents
+
+dncli ships with a skill that teaches AI coding agents how to use it
+safely: where ids come from, what costs money or deletes data, and to
+ask before changing anything. It works with Claude Code, Codex, Gemini
+CLI, GitHub Copilot, Cursor and OpenCode:
+
+```sh
+dncli skill install                      # every agent found on this machine
+dncli skill install --agent codex        # a specific agent; repeat for more
+dncli skill install --project            # into the current project instead
+```
+
+Run it again after upgrading dncli to update the skill; `dncli skill
+show` prints it.
+
 ## Certificates
 
 `dncli` issues Let's Encrypt certificates using the DNS-01 challenge:

{devnomads_cli-0.9.1 → devnomads_cli-0.11.0}/README.md

@@ -10,18 +10,43 @@ as **`devnomads-cli`**.
 
 ## Install
 
+Install dncli with [uv](https://docs.astral.sh/uv/). It gives dncli
+its own isolated environment and puts the `dncli` command on your
+PATH:
+
 ```sh
-pip install devnomads-cli
+uv tool install devnomads-cli
 ```
 
-For a global, isolated install (recommended on workstations), use
-[uv](https://docs.astral.sh/uv/) or pipx instead - same result, no
-interference with system packages:
+No uv yet? Install it first:
+
+```sh
+curl -LsSf https://astral.sh/uv/install.sh | sh                               # macOS, Linux
+powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"  # Windows
+```
+
+pipx (`pipx install devnomads-cli`) and pip (`pip install
+devnomads-cli`) work as well.
+
+### Updates
+
+Update with:
 
 ```sh
-uv tool install devnomads-cli   # or: pipx install devnomads-cli
+uv tool upgrade devnomads-cli
 ```
 
+dncli checks PyPI at most once a day and tells you when a new version
+is out, with the command to update the way you installed it. It only
+does so on an interactive terminal, never in pipes, scripts or CI; set
+`DN_NO_UPDATE_CHECK=1` to turn it off.
+
+dncli also warns when the DevNomads API reports a major version it was
+not built for, and tells you when the API no longer supports your
+dncli version. Update dncli in both cases.
+
+### Shell completion
+
 Enable shell completion (bash, zsh, fish, PowerShell):
 
 ```sh
@@ -49,7 +74,8 @@ dncli containers show <id>
 
 Every DevNomads product has its own command group - `apps`,
 `buckets`, `containers`, `databases`, `domains`, `emails`,
-`forwards`, `proxies`, `servers`, `sites` and more. Explore with
+`forwards`, `proxies`, `servers`, `sites` and more, plus `keys` for
+your SSH keys and `jobs` for background work. Explore with
 `dncli --help` and `dncli <group> --help`.
 
 Commands accept any unambiguous prefix: `dncli e l` is `dncli emails
@@ -65,6 +91,18 @@ dncli dns records set example.com www A 192.0.2.1 --ttl 3600
 dncli dns records delete example.com www A
 ```
 
+Anywhere a zone is expected you may pass the service id of a domain
+instead of its name, so the ids from `dncli domains list` work here
+too:
+
+```sh
+dncli dns records list 42
+```
+
+An id always means that domain's own zone. A delegated subzone such
+as `foo.example.com` has no domain service of its own, so address it
+by name.
+
 ## Moving a zone from another provider
 
 `dncli dns transfer` copies a zone from your current DNS provider
@@ -92,6 +130,17 @@ dncli services list --profile acme
 export DN_PROFILE=acme
 ```
 
+Manage stored profiles:
+
+```sh
+dncli configure list                 # profiles, with keys masked
+dncli configure set-key acme         # replace a profile's API key
+dncli configure delete acme          # remove a profile
+```
+
+`set-key --stdin` reads the new key from standard input, and
+`delete --yes` skips the question, for use in scripts.
+
 ## Scripting
 
 Output is a human-readable table on a terminal and JSON when piped,
@@ -115,9 +164,23 @@ fields, and reports an error on an unknown column name.
 
 Commands that take a service id also accept a unique entity name and
 resolve it for you, so `dncli domains show example.com` works as well
-as `dncli domains show 1234`. A purely numeric value is always treated
-as an id; an entity that matches more than one service is rejected, so
-pass the id when an entity is not unique.
+as `dncli domains show 1234`. Names match regardless of case. A purely
+numeric value is always treated as an id; an entity that matches more
+than one service is rejected, so pass the id when an entity is not
+unique. Other references, such as cluster, key or user ids, take the
+numeric id only.
+
+Some changes run in the background: creating a site, server, proxy or
+domain, for example, queues one or more jobs in a batch. Such a command
+prints the queued jobs and returns right away; add `--wait` to follow
+the batch until every job has finished and see how each one ended.
+With `--wait` the exit status is 0 only when every job completed. You
+can look a batch up later with `dncli jobs batches show <batch_id>`.
+
+The exit status is 0 when the API accepted the request and 1 for any
+error response, so `dncli ... && next-step` is safe in scripts. Every
+command takes `--timeout <seconds>` (default 300) for how long to wait
+for the API, including the time spent waiting on `--wait`.
 
 In CI and pipelines, skip the credentials file and pass the key via
 the environment:
@@ -127,6 +190,22 @@ export DN_API_KEY=...        # beats any stored profile
 dncli services list | jq -r '.[].entity'
 ```
 
+## AI agents
+
+dncli ships with a skill that teaches AI coding agents how to use it
+safely: where ids come from, what costs money or deletes data, and to
+ask before changing anything. It works with Claude Code, Codex, Gemini
+CLI, GitHub Copilot, Cursor and OpenCode:
+
+```sh
+dncli skill install                      # every agent found on this machine
+dncli skill install --agent codex        # a specific agent; repeat for more
+dncli skill install --project            # into the current project instead
+```
+
+Run it again after upgrading dncli to update the skill; `dncli skill
+show` prints it.
+
 ## Certificates
 
 `dncli` issues Let's Encrypt certificates using the DNS-01 challenge:

{devnomads_cli-0.9.1 → devnomads_cli-0.11.0}/devnomads_cli.egg-info/PKG-INFO

@@ -1,17 +1,17 @@
 Metadata-Version: 2.4
 Name: devnomads-cli
-Version: 0.9.1
+Version: 0.11.0
 Summary: Manage your DevNomads services from the command line
 Author-email: DevNomads <support@devnomads.nl>
 License: MIT
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: typer>=0.12
+Requires-Dist: typer>=0.19
 Requires-Dist: httpx>=0.27
 Requires-Dist: rich>=13
 Requires-Dist: cryptography>=42
-Requires-Dist: devnomads[acme]>=0.5.0
+Requires-Dist: devnomads[acme]>=0.6.0
 Dynamic: license-file
 
 # dncli
@@ -26,18 +26,43 @@ as **`devnomads-cli`**.
 
 ## Install
 
+Install dncli with [uv](https://docs.astral.sh/uv/). It gives dncli
+its own isolated environment and puts the `dncli` command on your
+PATH:
+
 ```sh
-pip install devnomads-cli
+uv tool install devnomads-cli
 ```
 
-For a global, isolated install (recommended on workstations), use
-[uv](https://docs.astral.sh/uv/) or pipx instead - same result, no
-interference with system packages:
+No uv yet? Install it first:
+
+```sh
+curl -LsSf https://astral.sh/uv/install.sh | sh                               # macOS, Linux
+powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"  # Windows
+```
+
+pipx (`pipx install devnomads-cli`) and pip (`pip install
+devnomads-cli`) work as well.
+
+### Updates
+
+Update with:
 
 ```sh
-uv tool install devnomads-cli   # or: pipx install devnomads-cli
+uv tool upgrade devnomads-cli
 ```
 
+dncli checks PyPI at most once a day and tells you when a new version
+is out, with the command to update the way you installed it. It only
+does so on an interactive terminal, never in pipes, scripts or CI; set
+`DN_NO_UPDATE_CHECK=1` to turn it off.
+
+dncli also warns when the DevNomads API reports a major version it was
+not built for, and tells you when the API no longer supports your
+dncli version. Update dncli in both cases.
+
+### Shell completion
+
 Enable shell completion (bash, zsh, fish, PowerShell):
 
 ```sh
@@ -65,7 +90,8 @@ dncli containers show <id>
 
 Every DevNomads product has its own command group - `apps`,
 `buckets`, `containers`, `databases`, `domains`, `emails`,
-`forwards`, `proxies`, `servers`, `sites` and more. Explore with
+`forwards`, `proxies`, `servers`, `sites` and more, plus `keys` for
+your SSH keys and `jobs` for background work. Explore with
 `dncli --help` and `dncli <group> --help`.
 
 Commands accept any unambiguous prefix: `dncli e l` is `dncli emails
@@ -81,6 +107,18 @@ dncli dns records set example.com www A 192.0.2.1 --ttl 3600
 dncli dns records delete example.com www A
 ```
 
+Anywhere a zone is expected you may pass the service id of a domain
+instead of its name, so the ids from `dncli domains list` work here
+too:
+
+```sh
+dncli dns records list 42
+```
+
+An id always means that domain's own zone. A delegated subzone such
+as `foo.example.com` has no domain service of its own, so address it
+by name.
+
 ## Moving a zone from another provider
 
 `dncli dns transfer` copies a zone from your current DNS provider
@@ -108,6 +146,17 @@ dncli services list --profile acme
 export DN_PROFILE=acme
 ```
 
+Manage stored profiles:
+
+```sh
+dncli configure list                 # profiles, with keys masked
+dncli configure set-key acme         # replace a profile's API key
+dncli configure delete acme          # remove a profile
+```
+
+`set-key --stdin` reads the new key from standard input, and
+`delete --yes` skips the question, for use in scripts.
+
 ## Scripting
 
 Output is a human-readable table on a terminal and JSON when piped,
@@ -131,9 +180,23 @@ fields, and reports an error on an unknown column name.
 
 Commands that take a service id also accept a unique entity name and
 resolve it for you, so `dncli domains show example.com` works as well
-as `dncli domains show 1234`. A purely numeric value is always treated
-as an id; an entity that matches more than one service is rejected, so
-pass the id when an entity is not unique.
+as `dncli domains show 1234`. Names match regardless of case. A purely
+numeric value is always treated as an id; an entity that matches more
+than one service is rejected, so pass the id when an entity is not
+unique. Other references, such as cluster, key or user ids, take the
+numeric id only.
+
+Some changes run in the background: creating a site, server, proxy or
+domain, for example, queues one or more jobs in a batch. Such a command
+prints the queued jobs and returns right away; add `--wait` to follow
+the batch until every job has finished and see how each one ended.
+With `--wait` the exit status is 0 only when every job completed. You
+can look a batch up later with `dncli jobs batches show <batch_id>`.
+
+The exit status is 0 when the API accepted the request and 1 for any
+error response, so `dncli ... && next-step` is safe in scripts. Every
+command takes `--timeout <seconds>` (default 300) for how long to wait
+for the API, including the time spent waiting on `--wait`.
 
 In CI and pipelines, skip the credentials file and pass the key via
 the environment:
@@ -143,6 +206,22 @@ export DN_API_KEY=...        # beats any stored profile
 dncli services list | jq -r '.[].entity'
 ```
 
+## AI agents
+
+dncli ships with a skill that teaches AI coding agents how to use it
+safely: where ids come from, what costs money or deletes data, and to
+ask before changing anything. It works with Claude Code, Codex, Gemini
+CLI, GitHub Copilot, Cursor and OpenCode:
+
+```sh
+dncli skill install                      # every agent found on this machine
+dncli skill install --agent codex        # a specific agent; repeat for more
+dncli skill install --project            # into the current project instead
+```
+
+Run it again after upgrading dncli to update the skill; `dncli skill
+show` prints it.
+
 ## Certificates
 
 `dncli` issues Let's Encrypt certificates using the DNS-01 challenge:

{devnomads_cli-0.9.1 → devnomads_cli-0.11.0}/devnomads_cli.egg-info/SOURCES.txt

@@ -15,4 +15,5 @@ tests/test_generate.py
 tests/test_generated_cli.py
 tests/test_helpers.py
 tests/test_hook.py
-tests/test_transfer.py
+tests/test_transfer.py
+tests/test_versions.py

{devnomads_cli-0.9.1 → devnomads_cli-0.11.0}/devnomads_cli.egg-info/requires.txt

@@ -1,5 +1,5 @@
-typer>=0.12
+typer>=0.19
 httpx>=0.27
 rich>=13
 cryptography>=42
-devnomads[acme]>=0.5.0
+devnomads[acme]>=0.6.0