valt0-client 1.0.0__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.
@@ -0,0 +1,11 @@
1
+ __pycache__/
2
+ *.py[cod]
3
+ .venv/
4
+ venv/
5
+ dist/
6
+ build/
7
+ *.egg-info/
8
+ .pytest_cache/
9
+ .mypy_cache/
10
+ .ruff_cache/
11
+ .DS_Store
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
@@ -0,0 +1,185 @@
1
+ Metadata-Version: 2.5
2
+ Name: valt0-client
3
+ Version: 1.0.0
4
+ Summary: Python client for Valt0: fetch secrets from a local Valt0 vault at runtime
5
+ Project-URL: Homepage, https://valt0.com
6
+ Project-URL: Issues, https://github.com/byte1620/valt0-issues/issues
7
+ Author: BYTE 1620
8
+ License-Expression: Apache-2.0
9
+ License-File: LICENSE
10
+ Keywords: client,secrets,valt0,vault
11
+ Classifier: Intended Audience :: Developers
12
+ Classifier: Operating System :: MacOS
13
+ Classifier: Operating System :: POSIX :: Linux
14
+ Classifier: Programming Language :: Python :: 3
15
+ Classifier: Programming Language :: Python :: 3 :: Only
16
+ Classifier: Programming Language :: Python :: 3.9
17
+ Classifier: Programming Language :: Python :: 3.10
18
+ Classifier: Programming Language :: Python :: 3.11
19
+ Classifier: Programming Language :: Python :: 3.12
20
+ Classifier: Programming Language :: Python :: 3.13
21
+ Classifier: Programming Language :: Python :: 3.14
22
+ Classifier: Topic :: Security
23
+ Classifier: Typing :: Typed
24
+ Requires-Python: >=3.9
25
+ Requires-Dist: cryptography>=42
26
+ Description-Content-Type: text/markdown
27
+
28
+ # valt0
29
+
30
+ Python client for **Valt0**. It fetches secrets from a local Valt0 vault at runtime, so you don't
31
+ have to keep them in `.env` files, config files, or CI variables.
32
+
33
+ - **License:** Apache-2.0
34
+ - **Requires:** Python >= 3.9, and the `valt0` service/CLI installed and running locally
35
+
36
+ ---
37
+
38
+ ## Installation
39
+
40
+ ```bash
41
+ pip install valt0-client
42
+ ```
43
+
44
+ The package is installed as `valt0-client` and imported as `valt0`.
45
+
46
+ ---
47
+
48
+ ## Usage
49
+
50
+ ```python
51
+ import valt0
52
+
53
+ vault = valt0.open_vault(id="your-vault-id", name="your-vault-name")
54
+
55
+ # The with block zeroes the underlying buffer as soon as you are finished
56
+ with vault.secret("DATABASE_PASSWORD") as secret:
57
+ # Preferred: the raw bytes, wiped on exit
58
+ pw = secret.bytes()
59
+
60
+ # Or, when a string is unavoidable
61
+ db.connect(password=secret.reveal())
62
+ ```
63
+
64
+ Without a `with` block, call `secret.destroy()` yourself, ideally in a `finally`.
65
+
66
+ ### Secrets are redacted by default
67
+
68
+ A `Secret` won't leak its value into a log line, a traceback, an f-string, or a pickle. You only
69
+ get the plaintext when you ask for it explicitly:
70
+
71
+ ```python
72
+ print(secret) # [REDACTED]
73
+ print(repr(secret)) # Secret([REDACTED])
74
+ f"{secret}" # [REDACTED]
75
+ logging.info("connecting %s", secret) # connecting [REDACTED]
76
+ json.dumps({"pw": secret}, default=str) # {"pw": "[REDACTED]"}
77
+ pickle.dumps(secret) # TypeError: Secret objects cannot be pickled or copied
78
+
79
+ secret.reveal() # the actual value
80
+ ```
81
+
82
+ Redaction covers `str()`, `repr()` and `format()`. Pickling and copying raise `TypeError`, so a
83
+ secret can't slip out through `multiprocessing` or a cache.
84
+
85
+ ### Errors
86
+
87
+ `open_vault` and `Vault.secret` raise two specific errors for the most common connection failures:
88
+
89
+ ```python
90
+ try:
91
+ vault = valt0.open_vault(id="your-vault-id", name="your-vault-name")
92
+ except valt0.CantConnectToServiceError:
93
+ ... # socket or session file not found: is the valt0 service running?
94
+ except valt0.NoServiceResponseError:
95
+ ... # the service did not answer within the transport timeout (1s)
96
+ except valt0.Valt0Error:
97
+ ... # any other error, e.g. the vault could not be loaded
98
+ ```
99
+
100
+ ### Threads and asyncio
101
+
102
+ The client is synchronous and thread-safe; every call uses its own connection. From async code,
103
+ run it in a worker thread:
104
+
105
+ ```python
106
+ secret = await asyncio.to_thread(vault.secret, "DATABASE_PASSWORD")
107
+ ```
108
+
109
+ ---
110
+
111
+ ## API
112
+
113
+ ### `open_vault(*, id: str, name: str) -> Vault`
114
+
115
+ Opens the vault identified by `id`.
116
+ Raises an error if the service is unreachable or the vault cannot be loaded.
117
+
118
+ | Argument | Type | Description |
119
+ | -------- | ----- | ----------------------------------------------------------- |
120
+ | `id` | `str` | Vault identifier — the only value used to locate the vault |
121
+ | `name` | `str` | Display label for messages; `.valt0` is appended if missing |
122
+
123
+ > **Note:** `name` can be anything. Valt0 does not check that it matches the vault `id` — it is
124
+ > only used for messaging purposes, so pick whatever makes the vault easy to recognise.
125
+
126
+ ### `Vault`
127
+
128
+ | Member | Description |
129
+ | -------------- | ------------------------------------ |
130
+ | `id` | The vault's id |
131
+ | `name` | The vault's name |
132
+ | `secret(name)` | `Secret`: fetches one secret by name |
133
+
134
+ ### `Secret`
135
+
136
+ | Member | Description |
137
+ | ------------- | ----------------------------------------------------------------------------------------------------------------- |
138
+ | `bytes()` | The raw bytes as a `bytearray` (the underlying buffer, not a copy). This is the preferred accessor. |
139
+ | `reveal()` | The value as a `str`. Strings are immutable and can't be wiped, so use sparingly. `ValueError` if not UTF-8 text. |
140
+ | `destroy()` | Zeroes the buffer. Buffers returned by `bytes()` are zeroed too, and later calls return empty values. |
141
+ | `with secret` | Calls `destroy()` when the block exits. |
142
+
143
+ ### Errors
144
+
145
+ | Error | Raised when |
146
+ | --------------------------- | ------------------------------------------------- |
147
+ | `Valt0Error` | Base class of every error the client raises |
148
+ | `CantConnectToServiceError` | The service socket or session file does not exist |
149
+ | `NoServiceResponseError` | The service did not respond before the deadline |
150
+
151
+ ---
152
+
153
+ ## Platform support
154
+
155
+ Linux, macOS and Windows, including inside containers.
156
+
157
+ On Linux and macOS the client reaches the service through its unix socket, or over TCP to
158
+ `host.docker.internal` when `VALT0_TRANSPORT_CHANNEL=tcp`. On Windows it always uses TCP to
159
+ `127.0.0.1` (CPython has no `AF_UNIX` support there), and `VALT0_TRANSPORT_CHANNEL` and
160
+ `VALT0_SOCKET_PATH` are ignored.
161
+
162
+ ---
163
+
164
+ ## Development
165
+
166
+ ```bash
167
+ python -m venv .venv && . .venv/bin/activate
168
+ pip install -e . pytest
169
+ pytest
170
+ ```
171
+
172
+ The tests run against a strict fake of the Valt0 service (`tests/fake_service.py`).
173
+ `tests/test_go_parity.py` also runs the Go client through the same scenarios and checks that both
174
+ clients send the same requests and return the same results; it runs when `go` is installed and the
175
+ Go client is checked out at `../../golang/client` (or `$VALT0_GO_CLIENT_DIR`). See
176
+ [RELEASING.md](RELEASING.md) for publishing.
177
+
178
+ ---
179
+
180
+ ## Links
181
+
182
+ - [Website](https://valt0.com)
183
+ - [Issue tracker](https://github.com/byte1620/valt0-issues/issues)
184
+
185
+ Maintained by BYTE 1620. Licensed under Apache-2.0.
@@ -0,0 +1,158 @@
1
+ # valt0
2
+
3
+ Python client for **Valt0**. It fetches secrets from a local Valt0 vault at runtime, so you don't
4
+ have to keep them in `.env` files, config files, or CI variables.
5
+
6
+ - **License:** Apache-2.0
7
+ - **Requires:** Python >= 3.9, and the `valt0` service/CLI installed and running locally
8
+
9
+ ---
10
+
11
+ ## Installation
12
+
13
+ ```bash
14
+ pip install valt0-client
15
+ ```
16
+
17
+ The package is installed as `valt0-client` and imported as `valt0`.
18
+
19
+ ---
20
+
21
+ ## Usage
22
+
23
+ ```python
24
+ import valt0
25
+
26
+ vault = valt0.open_vault(id="your-vault-id", name="your-vault-name")
27
+
28
+ # The with block zeroes the underlying buffer as soon as you are finished
29
+ with vault.secret("DATABASE_PASSWORD") as secret:
30
+ # Preferred: the raw bytes, wiped on exit
31
+ pw = secret.bytes()
32
+
33
+ # Or, when a string is unavoidable
34
+ db.connect(password=secret.reveal())
35
+ ```
36
+
37
+ Without a `with` block, call `secret.destroy()` yourself, ideally in a `finally`.
38
+
39
+ ### Secrets are redacted by default
40
+
41
+ A `Secret` won't leak its value into a log line, a traceback, an f-string, or a pickle. You only
42
+ get the plaintext when you ask for it explicitly:
43
+
44
+ ```python
45
+ print(secret) # [REDACTED]
46
+ print(repr(secret)) # Secret([REDACTED])
47
+ f"{secret}" # [REDACTED]
48
+ logging.info("connecting %s", secret) # connecting [REDACTED]
49
+ json.dumps({"pw": secret}, default=str) # {"pw": "[REDACTED]"}
50
+ pickle.dumps(secret) # TypeError: Secret objects cannot be pickled or copied
51
+
52
+ secret.reveal() # the actual value
53
+ ```
54
+
55
+ Redaction covers `str()`, `repr()` and `format()`. Pickling and copying raise `TypeError`, so a
56
+ secret can't slip out through `multiprocessing` or a cache.
57
+
58
+ ### Errors
59
+
60
+ `open_vault` and `Vault.secret` raise two specific errors for the most common connection failures:
61
+
62
+ ```python
63
+ try:
64
+ vault = valt0.open_vault(id="your-vault-id", name="your-vault-name")
65
+ except valt0.CantConnectToServiceError:
66
+ ... # socket or session file not found: is the valt0 service running?
67
+ except valt0.NoServiceResponseError:
68
+ ... # the service did not answer within the transport timeout (1s)
69
+ except valt0.Valt0Error:
70
+ ... # any other error, e.g. the vault could not be loaded
71
+ ```
72
+
73
+ ### Threads and asyncio
74
+
75
+ The client is synchronous and thread-safe; every call uses its own connection. From async code,
76
+ run it in a worker thread:
77
+
78
+ ```python
79
+ secret = await asyncio.to_thread(vault.secret, "DATABASE_PASSWORD")
80
+ ```
81
+
82
+ ---
83
+
84
+ ## API
85
+
86
+ ### `open_vault(*, id: str, name: str) -> Vault`
87
+
88
+ Opens the vault identified by `id`.
89
+ Raises an error if the service is unreachable or the vault cannot be loaded.
90
+
91
+ | Argument | Type | Description |
92
+ | -------- | ----- | ----------------------------------------------------------- |
93
+ | `id` | `str` | Vault identifier — the only value used to locate the vault |
94
+ | `name` | `str` | Display label for messages; `.valt0` is appended if missing |
95
+
96
+ > **Note:** `name` can be anything. Valt0 does not check that it matches the vault `id` — it is
97
+ > only used for messaging purposes, so pick whatever makes the vault easy to recognise.
98
+
99
+ ### `Vault`
100
+
101
+ | Member | Description |
102
+ | -------------- | ------------------------------------ |
103
+ | `id` | The vault's id |
104
+ | `name` | The vault's name |
105
+ | `secret(name)` | `Secret`: fetches one secret by name |
106
+
107
+ ### `Secret`
108
+
109
+ | Member | Description |
110
+ | ------------- | ----------------------------------------------------------------------------------------------------------------- |
111
+ | `bytes()` | The raw bytes as a `bytearray` (the underlying buffer, not a copy). This is the preferred accessor. |
112
+ | `reveal()` | The value as a `str`. Strings are immutable and can't be wiped, so use sparingly. `ValueError` if not UTF-8 text. |
113
+ | `destroy()` | Zeroes the buffer. Buffers returned by `bytes()` are zeroed too, and later calls return empty values. |
114
+ | `with secret` | Calls `destroy()` when the block exits. |
115
+
116
+ ### Errors
117
+
118
+ | Error | Raised when |
119
+ | --------------------------- | ------------------------------------------------- |
120
+ | `Valt0Error` | Base class of every error the client raises |
121
+ | `CantConnectToServiceError` | The service socket or session file does not exist |
122
+ | `NoServiceResponseError` | The service did not respond before the deadline |
123
+
124
+ ---
125
+
126
+ ## Platform support
127
+
128
+ Linux, macOS and Windows, including inside containers.
129
+
130
+ On Linux and macOS the client reaches the service through its unix socket, or over TCP to
131
+ `host.docker.internal` when `VALT0_TRANSPORT_CHANNEL=tcp`. On Windows it always uses TCP to
132
+ `127.0.0.1` (CPython has no `AF_UNIX` support there), and `VALT0_TRANSPORT_CHANNEL` and
133
+ `VALT0_SOCKET_PATH` are ignored.
134
+
135
+ ---
136
+
137
+ ## Development
138
+
139
+ ```bash
140
+ python -m venv .venv && . .venv/bin/activate
141
+ pip install -e . pytest
142
+ pytest
143
+ ```
144
+
145
+ The tests run against a strict fake of the Valt0 service (`tests/fake_service.py`).
146
+ `tests/test_go_parity.py` also runs the Go client through the same scenarios and checks that both
147
+ clients send the same requests and return the same results; it runs when `go` is installed and the
148
+ Go client is checked out at `../../golang/client` (or `$VALT0_GO_CLIENT_DIR`). See
149
+ [RELEASING.md](RELEASING.md) for publishing.
150
+
151
+ ---
152
+
153
+ ## Links
154
+
155
+ - [Website](https://valt0.com)
156
+ - [Issue tracker](https://github.com/byte1620/valt0-issues/issues)
157
+
158
+ Maintained by BYTE 1620. Licensed under Apache-2.0.
@@ -0,0 +1,58 @@
1
+ [build-system]
2
+ requires = ["hatchling>=1.27"]
3
+ build-backend = "hatchling.build"
4
+
5
+ [project]
6
+ name = "valt0-client" # distribution name; the import name is still `valt0`
7
+ dynamic = ["version"]
8
+ description = "Python client for Valt0: fetch secrets from a local Valt0 vault at runtime"
9
+ readme = "README.md"
10
+ license = "Apache-2.0"
11
+ license-files = ["LICENSE"]
12
+ authors = [{ name = "BYTE 1620" }]
13
+ requires-python = ">=3.9"
14
+ dependencies = ["cryptography>=42"]
15
+ keywords = ["valt0", "vault", "secrets", "client"]
16
+ classifiers = [
17
+ "Intended Audience :: Developers",
18
+ "Operating System :: MacOS",
19
+ "Operating System :: POSIX :: Linux",
20
+ "Programming Language :: Python :: 3",
21
+ "Programming Language :: Python :: 3 :: Only",
22
+ "Programming Language :: Python :: 3.9",
23
+ "Programming Language :: Python :: 3.10",
24
+ "Programming Language :: Python :: 3.11",
25
+ "Programming Language :: Python :: 3.12",
26
+ "Programming Language :: Python :: 3.13",
27
+ "Programming Language :: Python :: 3.14",
28
+ "Topic :: Security",
29
+ "Typing :: Typed",
30
+ ]
31
+
32
+ [project.urls]
33
+ Homepage = "https://valt0.com"
34
+ Issues = "https://github.com/byte1620/valt0-issues/issues"
35
+
36
+ [dependency-groups]
37
+ test = ["pytest>=8"]
38
+
39
+ [tool.hatch.version]
40
+ path = "src/valt0/__init__.py"
41
+
42
+ [tool.hatch.build.targets.wheel]
43
+ # The distribution is valt0-client but the package is valt0, so hatchling needs telling.
44
+ packages = ["src/valt0"]
45
+
46
+ [tool.hatch.build.targets.sdist]
47
+ include = ["src", "tests", "README.md", "LICENSE"]
48
+
49
+ [tool.pytest.ini_options]
50
+ testpaths = ["tests"]
51
+
52
+ [tool.ruff]
53
+ line-length = 120
54
+ target-version = "py39"
55
+
56
+ [tool.mypy]
57
+ strict = true
58
+ files = ["src"]
@@ -0,0 +1,26 @@
1
+ """Python client for Valt0.
2
+
3
+ Fetches secrets from a local Valt0 vault at runtime, so you don't have to keep them in ``.env``
4
+ files, config files, or CI variables::
5
+
6
+ import valt0
7
+
8
+ vault = valt0.open_vault(id="your-vault-id", name="your-vault-name")
9
+ with vault.secret("DATABASE_PASSWORD") as secret:
10
+ db.connect(password=secret.reveal())
11
+ """
12
+
13
+ from ._errors import CantConnectToServiceError, NoServiceResponseError, Valt0Error
14
+ from ._secret import Secret
15
+ from ._vault import Vault, open_vault
16
+
17
+ __version__ = "1.0.0"
18
+
19
+ __all__ = [
20
+ "CantConnectToServiceError",
21
+ "NoServiceResponseError",
22
+ "Secret",
23
+ "Valt0Error",
24
+ "Vault",
25
+ "open_vault",
26
+ ]
@@ -0,0 +1,6 @@
1
+ """Constants. Port of internal/config/constants.go."""
2
+
3
+ VAULT_FILE_EXT = ".valt0"
4
+
5
+ # Seconds allowed to connect to the service, and again for the request/response exchange.
6
+ TRANSPORT_TIMEOUT = 1.0