devnomads-cli 0.5.5__tar.gz → 0.5.8__tar.gz

{devnomads_cli-0.5.5 → devnomads_cli-0.5.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devnomads-cli
-Version: 0.5.5
+Version: 0.5.8
 Summary: Manage your DevNomads services from the command line
 Author-email: DevNomads <support@devnomads.nl>
 License: MIT
@@ -11,7 +11,7 @@ Requires-Dist: typer>=0.12
 Requires-Dist: httpx>=0.27
 Requires-Dist: rich>=13
 Requires-Dist: cryptography>=42
-Requires-Dist: devnomads[acme]>=0.2.3
+Requires-Dist: devnomads[acme]>=0.2.5
 Dynamic: license-file
 
 # dncli
@@ -111,15 +111,29 @@ export DN_PROFILE=acme
 ## Scripting
 
 Output is a human-readable table on a terminal and JSON when piped,
-so pipelines get parseable output without any flags; `--json` and
-`--table` force either. Data goes to stdout, everything else
-(warnings, prompts, status messages) to stderr, so `dncli ... | jq .`
-is always safe.
+so pipelines get parseable output without any flags; `--out
+table|json|csv|tsv` forces a specific format. Data goes to stdout,
+everything else (warnings, prompts, status messages) to stderr, so
+`dncli ... | jq .` is always safe.
+
+The `csv` and `tsv` formats use the same columns as the table view, so
+`dncli servers list --out csv` is ready for a spreadsheet.
 
 List tables show a focused set of columns: fields that are empty for
 every row, and nested collections (a server's IPs, a container's
 instances, a mailbox list) are left out of the overview. Use `<group>
-show <id>` or `--json` for the complete record.
+show <id>` or `--out json` for the complete record.
+
+To pick exactly the columns you want, pass `--columns` (`-c`) a
+comma-separated list, e.g. `dncli services list -c entity,started_at`.
+It applies to every format, projecting json and csv/tsv to just those
+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.
 
 In CI and pipelines, skip the credentials file and pass the key via
 the environment:
@@ -154,11 +168,33 @@ progress.
 Keys are ECDSA P-384 by default. Pick another with `--key-type`
 (`ecdsa256`, `ecdsa384`, `ecdsa521`, `rsa2048`, `rsa4096`).
 
+Let's Encrypt is the certificate authority by default. Pass
+`--provider zerossl` to use ZeroSSL instead. ZeroSSL requires External
+Account Binding credentials (create an EAB key pair in the ZeroSSL
+dashboard under Developer > EAB Credentials), supplied with `--eab-kid`
+and `--eab-hmac-key` or the `DN_ZEROSSL_EAB_KID` and
+`DN_ZEROSSL_EAB_HMAC_KEY` environment variables:
+
+```sh
+dncli cert issue example.com --provider zerossl \
+  --eab-kid <kid> --eab-hmac-key <hmac>
+```
+
+`--staging` (the Let's Encrypt staging CA) applies only to the
+letsencrypt provider. `cert renew` takes the same `--provider` and EAB
+options.
+
+Each CA gets its own ACME account: the key lives in
+`~/.config/dncli/acme/` as `account.pem` for Let's Encrypt production
+and `account-<provider>.pem` for ZeroSSL and the staging CA.
+
 Re-running `cert issue` is a no-op while the existing certificate is
 still valid for more than 21 days; pass `--force` to re-issue anyway.
 
 List what you have issued and re-export any of them - as a PEM bundle
-or a PKCS#12 (`.pfx`) file - without re-issuing:
+or a PKCS#12 (`.pfx`) file - without re-issuing. `cert list` includes a
+`provider` column showing the issuing CA (recorded at issue time, or
+inferred from the certificate's issuer for older certificates):
 
 ```sh
 dncli cert list

{devnomads_cli-0.5.5 → devnomads_cli-0.5.8}/README.md

@@ -95,15 +95,29 @@ export DN_PROFILE=acme
 ## Scripting
 
 Output is a human-readable table on a terminal and JSON when piped,
-so pipelines get parseable output without any flags; `--json` and
-`--table` force either. Data goes to stdout, everything else
-(warnings, prompts, status messages) to stderr, so `dncli ... | jq .`
-is always safe.
+so pipelines get parseable output without any flags; `--out
+table|json|csv|tsv` forces a specific format. Data goes to stdout,
+everything else (warnings, prompts, status messages) to stderr, so
+`dncli ... | jq .` is always safe.
+
+The `csv` and `tsv` formats use the same columns as the table view, so
+`dncli servers list --out csv` is ready for a spreadsheet.
 
 List tables show a focused set of columns: fields that are empty for
 every row, and nested collections (a server's IPs, a container's
 instances, a mailbox list) are left out of the overview. Use `<group>
-show <id>` or `--json` for the complete record.
+show <id>` or `--out json` for the complete record.
+
+To pick exactly the columns you want, pass `--columns` (`-c`) a
+comma-separated list, e.g. `dncli services list -c entity,started_at`.
+It applies to every format, projecting json and csv/tsv to just those
+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.
 
 In CI and pipelines, skip the credentials file and pass the key via
 the environment:
@@ -138,11 +152,33 @@ progress.
 Keys are ECDSA P-384 by default. Pick another with `--key-type`
 (`ecdsa256`, `ecdsa384`, `ecdsa521`, `rsa2048`, `rsa4096`).
 
+Let's Encrypt is the certificate authority by default. Pass
+`--provider zerossl` to use ZeroSSL instead. ZeroSSL requires External
+Account Binding credentials (create an EAB key pair in the ZeroSSL
+dashboard under Developer > EAB Credentials), supplied with `--eab-kid`
+and `--eab-hmac-key` or the `DN_ZEROSSL_EAB_KID` and
+`DN_ZEROSSL_EAB_HMAC_KEY` environment variables:
+
+```sh
+dncli cert issue example.com --provider zerossl \
+  --eab-kid <kid> --eab-hmac-key <hmac>
+```
+
+`--staging` (the Let's Encrypt staging CA) applies only to the
+letsencrypt provider. `cert renew` takes the same `--provider` and EAB
+options.
+
+Each CA gets its own ACME account: the key lives in
+`~/.config/dncli/acme/` as `account.pem` for Let's Encrypt production
+and `account-<provider>.pem` for ZeroSSL and the staging CA.
+
 Re-running `cert issue` is a no-op while the existing certificate is
 still valid for more than 21 days; pass `--force` to re-issue anyway.
 
 List what you have issued and re-export any of them - as a PEM bundle
-or a PKCS#12 (`.pfx`) file - without re-issuing:
+or a PKCS#12 (`.pfx`) file - without re-issuing. `cert list` includes a
+`provider` column showing the issuing CA (recorded at issue time, or
+inferred from the certificate's issuer for older certificates):
 
 ```sh
 dncli cert list

{devnomads_cli-0.5.5 → devnomads_cli-0.5.8}/devnomads_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devnomads-cli
-Version: 0.5.5
+Version: 0.5.8
 Summary: Manage your DevNomads services from the command line
 Author-email: DevNomads <support@devnomads.nl>
 License: MIT
@@ -11,7 +11,7 @@ Requires-Dist: typer>=0.12
 Requires-Dist: httpx>=0.27
 Requires-Dist: rich>=13
 Requires-Dist: cryptography>=42
-Requires-Dist: devnomads[acme]>=0.2.3
+Requires-Dist: devnomads[acme]>=0.2.5
 Dynamic: license-file
 
 # dncli
@@ -111,15 +111,29 @@ export DN_PROFILE=acme
 ## Scripting
 
 Output is a human-readable table on a terminal and JSON when piped,
-so pipelines get parseable output without any flags; `--json` and
-`--table` force either. Data goes to stdout, everything else
-(warnings, prompts, status messages) to stderr, so `dncli ... | jq .`
-is always safe.
+so pipelines get parseable output without any flags; `--out
+table|json|csv|tsv` forces a specific format. Data goes to stdout,
+everything else (warnings, prompts, status messages) to stderr, so
+`dncli ... | jq .` is always safe.
+
+The `csv` and `tsv` formats use the same columns as the table view, so
+`dncli servers list --out csv` is ready for a spreadsheet.
 
 List tables show a focused set of columns: fields that are empty for
 every row, and nested collections (a server's IPs, a container's
 instances, a mailbox list) are left out of the overview. Use `<group>
-show <id>` or `--json` for the complete record.
+show <id>` or `--out json` for the complete record.
+
+To pick exactly the columns you want, pass `--columns` (`-c`) a
+comma-separated list, e.g. `dncli services list -c entity,started_at`.
+It applies to every format, projecting json and csv/tsv to just those
+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.
 
 In CI and pipelines, skip the credentials file and pass the key via
 the environment:
@@ -154,11 +168,33 @@ progress.
 Keys are ECDSA P-384 by default. Pick another with `--key-type`
 (`ecdsa256`, `ecdsa384`, `ecdsa521`, `rsa2048`, `rsa4096`).
 
+Let's Encrypt is the certificate authority by default. Pass
+`--provider zerossl` to use ZeroSSL instead. ZeroSSL requires External
+Account Binding credentials (create an EAB key pair in the ZeroSSL
+dashboard under Developer > EAB Credentials), supplied with `--eab-kid`
+and `--eab-hmac-key` or the `DN_ZEROSSL_EAB_KID` and
+`DN_ZEROSSL_EAB_HMAC_KEY` environment variables:
+
+```sh
+dncli cert issue example.com --provider zerossl \
+  --eab-kid <kid> --eab-hmac-key <hmac>
+```
+
+`--staging` (the Let's Encrypt staging CA) applies only to the
+letsencrypt provider. `cert renew` takes the same `--provider` and EAB
+options.
+
+Each CA gets its own ACME account: the key lives in
+`~/.config/dncli/acme/` as `account.pem` for Let's Encrypt production
+and `account-<provider>.pem` for ZeroSSL and the staging CA.
+
 Re-running `cert issue` is a no-op while the existing certificate is
 still valid for more than 21 days; pass `--force` to re-issue anyway.
 
 List what you have issued and re-export any of them - as a PEM bundle
-or a PKCS#12 (`.pfx`) file - without re-issuing:
+or a PKCS#12 (`.pfx`) file - without re-issuing. `cert list` includes a
+`provider` column showing the issuing CA (recorded at issue time, or
+inferred from the certificate's issuer for older certificates):
 
 ```sh
 dncli cert list

{devnomads_cli-0.5.5 → devnomads_cli-0.5.8}/devnomads_cli.egg-info/requires.txt

@@ -2,4 +2,4 @@ typer>=0.12
 httpx>=0.27
 rich>=13
 cryptography>=42
-devnomads[acme]>=0.2.3
+devnomads[acme]>=0.2.5