devnomads-cli 0.4.1__tar.gz → 0.5.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (21) hide show
  1. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/PKG-INFO +31 -6
  2. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/README.md +30 -5
  3. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/devnomads_cli.egg-info/PKG-INFO +31 -6
  4. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/dncli.py +364 -62
  5. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/pyproject.toml +1 -1
  6. devnomads_cli-0.5.1/tests/test_cert.py +550 -0
  7. devnomads_cli-0.4.1/tests/test_cert.py +0 -254
  8. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/LICENSE +0 -0
  9. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/devnomads_cli.egg-info/SOURCES.txt +0 -0
  10. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/devnomads_cli.egg-info/dependency_links.txt +0 -0
  11. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/devnomads_cli.egg-info/entry_points.txt +0 -0
  12. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/devnomads_cli.egg-info/requires.txt +0 -0
  13. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/devnomads_cli.egg-info/top_level.txt +0 -0
  14. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/setup.cfg +0 -0
  15. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/tests/test_cli.py +0 -0
  16. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/tests/test_config.py +0 -0
  17. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/tests/test_generate.py +0 -0
  18. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/tests/test_generated_cli.py +0 -0
  19. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/tests/test_helpers.py +0 -0
  20. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/tests/test_hook.py +0 -0
  21. {devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/tests/test_transfer.py +0 -0
{devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: devnomads-cli
3
- Version: 0.4.1
3
+ Version: 0.5.1
4
4
  Summary: Manage your DevNomads services from the command line
5
5
  Author-email: DevNomads <support@devnomads.nl>
6
6
  License: MIT
@@ -126,21 +126,46 @@ dncli services list | jq -r '.[].entity'
126
126
 
127
127
  ## Certificates
128
128
 
129
- `dncli` issues Let's Encrypt certificates over DNS-01 and HTTP-01:
129
+ `dncli` issues Let's Encrypt certificates using the DNS-01 challenge:
130
130
 
131
131
  ```sh
132
132
  dncli cert issue example.com -d www.example.com -d "*.example.com"
133
133
  ```
134
134
 
135
135
  The first argument is the primary domain (the certificate CN); add
136
- extra names (SANs) by repeating `--san`/`-d`. The certificate is
137
- written to `~/.config/dncli/certs/<domain>/` as `cert.pem`,
138
- `fullchain.pem`, `chain.pem`, and `privkey.pem` (0600); override the
139
- location with `--out`.
136
+ extra names (SANs) by repeating `--san`/`-d`. Every name must live in
137
+ one of your DevNomads DNS zones, and that zone must be delegated to the
138
+ DevNomads nameservers (`one.dns.infrapod.nl`, `two.dns.infrapod.nl`,
139
+ `three.dns.infrapod.eu`) - otherwise issuance is refused, since the
140
+ DNS-01 challenge records would not be visible to the CA.
141
+
142
+ The certificate is always written to `~/.config/dncli/certs/<domain>/`
143
+ as `cert.pem`, `fullchain.pem`, `chain.pem`, and `privkey.pem` (0600).
144
+ Pass `--out <file>` to additionally export a single PEM bundle of
145
+ exactly three blocks - the key, the certificate, and the issuing
146
+ intermediate, in that order. Add `-v`/`--verbose` for detailed ACME
147
+ progress.
140
148
 
141
149
  Keys are ECDSA P-384 by default. Pick another with `--key-type`
142
150
  (`ecdsa256`, `ecdsa384`, `ecdsa521`, `rsa2048`, `rsa4096`).
143
151
 
152
+ Re-running `cert issue` is a no-op while the existing certificate is
153
+ still valid for more than 21 days; pass `--force` to re-issue anyway.
154
+
155
+ List what you have issued and re-export any of them - as a PEM bundle
156
+ or a PKCS#12 (`.pfx`) file - without re-issuing:
157
+
158
+ ```sh
159
+ dncli cert list
160
+ dncli cert export example.com --out bundle.pem # omit --out to print
161
+ dncli cert export example.com --format pfx --out bundle.pfx
162
+ dncli cert export example.com --format pfx --out bundle.pfx --passphrase secret
163
+ ```
164
+
165
+ The `.pfx` is unencrypted unless you pass `--passphrase` (alias
166
+ `--password`). Both bundle formats carry the same three items: key,
167
+ certificate, and the issuing intermediate.
168
+
144
169
  A dehydrated-compatible DNS-01 hook ships as `dncli-dns-hook`:
145
170
 
146
171
  ```sh
{devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/README.md RENAMED
@@ -110,21 +110,46 @@ dncli services list | jq -r '.[].entity'
110
110
 
111
111
  ## Certificates
112
112
 
113
- `dncli` issues Let's Encrypt certificates over DNS-01 and HTTP-01:
113
+ `dncli` issues Let's Encrypt certificates using the DNS-01 challenge:
114
114
 
115
115
  ```sh
116
116
  dncli cert issue example.com -d www.example.com -d "*.example.com"
117
117
  ```
118
118
 
119
119
  The first argument is the primary domain (the certificate CN); add
120
- extra names (SANs) by repeating `--san`/`-d`. The certificate is
121
- written to `~/.config/dncli/certs/<domain>/` as `cert.pem`,
122
- `fullchain.pem`, `chain.pem`, and `privkey.pem` (0600); override the
123
- location with `--out`.
120
+ extra names (SANs) by repeating `--san`/`-d`. Every name must live in
121
+ one of your DevNomads DNS zones, and that zone must be delegated to the
122
+ DevNomads nameservers (`one.dns.infrapod.nl`, `two.dns.infrapod.nl`,
123
+ `three.dns.infrapod.eu`) - otherwise issuance is refused, since the
124
+ DNS-01 challenge records would not be visible to the CA.
125
+
126
+ The certificate is always written to `~/.config/dncli/certs/<domain>/`
127
+ as `cert.pem`, `fullchain.pem`, `chain.pem`, and `privkey.pem` (0600).
128
+ Pass `--out <file>` to additionally export a single PEM bundle of
129
+ exactly three blocks - the key, the certificate, and the issuing
130
+ intermediate, in that order. Add `-v`/`--verbose` for detailed ACME
131
+ progress.
124
132
 
125
133
  Keys are ECDSA P-384 by default. Pick another with `--key-type`
126
134
  (`ecdsa256`, `ecdsa384`, `ecdsa521`, `rsa2048`, `rsa4096`).
127
135
 
136
+ Re-running `cert issue` is a no-op while the existing certificate is
137
+ still valid for more than 21 days; pass `--force` to re-issue anyway.
138
+
139
+ List what you have issued and re-export any of them - as a PEM bundle
140
+ or a PKCS#12 (`.pfx`) file - without re-issuing:
141
+
142
+ ```sh
143
+ dncli cert list
144
+ dncli cert export example.com --out bundle.pem # omit --out to print
145
+ dncli cert export example.com --format pfx --out bundle.pfx
146
+ dncli cert export example.com --format pfx --out bundle.pfx --passphrase secret
147
+ ```
148
+
149
+ The `.pfx` is unencrypted unless you pass `--passphrase` (alias
150
+ `--password`). Both bundle formats carry the same three items: key,
151
+ certificate, and the issuing intermediate.
152
+
128
153
  A dehydrated-compatible DNS-01 hook ships as `dncli-dns-hook`:
129
154
 
130
155
  ```sh
{devnomads_cli-0.4.1 → devnomads_cli-0.5.1}/devnomads_cli.egg-info/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: devnomads-cli
3
- Version: 0.4.1
3
+ Version: 0.5.1
4
4
  Summary: Manage your DevNomads services from the command line
5
5
  Author-email: DevNomads <support@devnomads.nl>
6
6
  License: MIT
@@ -126,21 +126,46 @@ dncli services list | jq -r '.[].entity'
126
126
 
127
127
  ## Certificates
128
128
 
129
- `dncli` issues Let's Encrypt certificates over DNS-01 and HTTP-01:
129
+ `dncli` issues Let's Encrypt certificates using the DNS-01 challenge:
130
130
 
131
131
  ```sh
132
132
  dncli cert issue example.com -d www.example.com -d "*.example.com"
133
133
  ```
134
134
 
135
135
  The first argument is the primary domain (the certificate CN); add
136
- extra names (SANs) by repeating `--san`/`-d`. The certificate is
137
- written to `~/.config/dncli/certs/<domain>/` as `cert.pem`,
138
- `fullchain.pem`, `chain.pem`, and `privkey.pem` (0600); override the
139
- location with `--out`.
136
+ extra names (SANs) by repeating `--san`/`-d`. Every name must live in
137
+ one of your DevNomads DNS zones, and that zone must be delegated to the
138
+ DevNomads nameservers (`one.dns.infrapod.nl`, `two.dns.infrapod.nl`,
139
+ `three.dns.infrapod.eu`) - otherwise issuance is refused, since the
140
+ DNS-01 challenge records would not be visible to the CA.
141
+
142
+ The certificate is always written to `~/.config/dncli/certs/<domain>/`
143
+ as `cert.pem`, `fullchain.pem`, `chain.pem`, and `privkey.pem` (0600).
144
+ Pass `--out <file>` to additionally export a single PEM bundle of
145
+ exactly three blocks - the key, the certificate, and the issuing
146
+ intermediate, in that order. Add `-v`/`--verbose` for detailed ACME
147
+ progress.
140
148
 
141
149
  Keys are ECDSA P-384 by default. Pick another with `--key-type`
142
150
  (`ecdsa256`, `ecdsa384`, `ecdsa521`, `rsa2048`, `rsa4096`).
143
151
 
152
+ Re-running `cert issue` is a no-op while the existing certificate is
153
+ still valid for more than 21 days; pass `--force` to re-issue anyway.
154
+
155
+ List what you have issued and re-export any of them - as a PEM bundle
156
+ or a PKCS#12 (`.pfx`) file - without re-issuing:
157
+
158
+ ```sh
159
+ dncli cert list
160
+ dncli cert export example.com --out bundle.pem # omit --out to print
161
+ dncli cert export example.com --format pfx --out bundle.pfx
162
+ dncli cert export example.com --format pfx --out bundle.pfx --passphrase secret
163
+ ```
164
+
165
+ The `.pfx` is unencrypted unless you pass `--passphrase` (alias
166
+ `--password`). Both bundle formats carry the same three items: key,
167
+ certificate, and the issuing intermediate.
168
+
144
169
  A dehydrated-compatible DNS-01 hook ships as `dncli-dns-hook`:
145
170
 
146
171
  ```sh