opteryx-shared-services 0.1.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,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2025 Justin Joyce (@joocer)
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
@@ -0,0 +1,461 @@
1
+ Metadata-Version: 2.4
2
+ Name: opteryx-shared-services
3
+ Version: 0.1.0
4
+ Summary: Shared capabilities for Opteryx platform services
5
+ Author-email: joocer <justin.joyce@joocer.com>
6
+ License: Apache License
7
+ Version 2.0, January 2004
8
+ http://www.apache.org/licenses/
9
+
10
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
11
+
12
+ 1. Definitions.
13
+
14
+ "License" shall mean the terms and conditions for use, reproduction,
15
+ and distribution as defined by Sections 1 through 9 of this document.
16
+
17
+ "Licensor" shall mean the copyright owner or entity authorized by
18
+ the copyright owner that is granting the License.
19
+
20
+ "Legal Entity" shall mean the union of the acting entity and all
21
+ other entities that control, are controlled by, or are under common
22
+ control with that entity. For the purposes of this definition,
23
+ "control" means (i) the power, direct or indirect, to cause the
24
+ direction or management of such entity, whether by contract or
25
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
26
+ outstanding shares, or (iii) beneficial ownership of such entity.
27
+
28
+ "You" (or "Your") shall mean an individual or Legal Entity
29
+ exercising permissions granted by this License.
30
+
31
+ "Source" form shall mean the preferred form for making modifications,
32
+ including but not limited to software source code, documentation
33
+ source, and configuration files.
34
+
35
+ "Object" form shall mean any form resulting from mechanical
36
+ transformation or translation of a Source form, including but
37
+ not limited to compiled object code, generated documentation,
38
+ and conversions to other media types.
39
+
40
+ "Work" shall mean the work of authorship, whether in Source or
41
+ Object form, made available under the License, as indicated by a
42
+ copyright notice that is included in or attached to the work
43
+ (an example is provided in the Appendix below).
44
+
45
+ "Derivative Works" shall mean any work, whether in Source or Object
46
+ form, that is based on (or derived from) the Work and for which the
47
+ editorial revisions, annotations, elaborations, or other modifications
48
+ represent, as a whole, an original work of authorship. For the purposes
49
+ of this License, Derivative Works shall not include works that remain
50
+ separable from, or merely link (or bind by name) to the interfaces of,
51
+ the Work and Derivative Works thereof.
52
+
53
+ "Contribution" shall mean any work of authorship, including
54
+ the original version of the Work and any modifications or additions
55
+ to that Work or Derivative Works thereof, that is intentionally
56
+ submitted to Licensor for inclusion in the Work by the copyright owner
57
+ or by an individual or Legal Entity authorized to submit on behalf of
58
+ the copyright owner. For the purposes of this definition, "submitted"
59
+ means any form of electronic, verbal, or written communication sent
60
+ to the Licensor or its representatives, including but not limited to
61
+ communication on electronic mailing lists, source code control systems,
62
+ and issue tracking systems that are managed by, or on behalf of, the
63
+ Licensor for the purpose of discussing and improving the Work, but
64
+ excluding communication that is conspicuously marked or otherwise
65
+ designated in writing by the copyright owner as "Not a Contribution."
66
+
67
+ "Contributor" shall mean Licensor and any individual or Legal Entity
68
+ on behalf of whom a Contribution has been received by Licensor and
69
+ subsequently incorporated within the Work.
70
+
71
+ 2. Grant of Copyright License. Subject to the terms and conditions of
72
+ this License, each Contributor hereby grants to You a perpetual,
73
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
74
+ copyright license to reproduce, prepare Derivative Works of,
75
+ publicly display, publicly perform, sublicense, and distribute the
76
+ Work and such Derivative Works in Source or Object form.
77
+
78
+ 3. Grant of Patent License. Subject to the terms and conditions of
79
+ this License, each Contributor hereby grants to You a perpetual,
80
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
81
+ (except as stated in this section) patent license to make, have made,
82
+ use, offer to sell, sell, import, and otherwise transfer the Work,
83
+ where such license applies only to those patent claims licensable
84
+ by such Contributor that are necessarily infringed by their
85
+ Contribution(s) alone or by combination of their Contribution(s)
86
+ with the Work to which such Contribution(s) was submitted. If You
87
+ institute patent litigation against any entity (including a
88
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
89
+ or a Contribution incorporated within the Work constitutes direct
90
+ or contributory patent infringement, then any patent licenses
91
+ granted to You under this License for that Work shall terminate
92
+ as of the date such litigation is filed.
93
+
94
+ 4. Redistribution. You may reproduce and distribute copies of the
95
+ Work or Derivative Works thereof in any medium, with or without
96
+ modifications, and in Source or Object form, provided that You
97
+ meet the following conditions:
98
+
99
+ (a) You must give any other recipients of the Work or
100
+ Derivative Works a copy of this License; and
101
+
102
+ (b) You must cause any modified files to carry prominent notices
103
+ stating that You changed the files; and
104
+
105
+ (c) You must retain, in the Source form of any Derivative Works
106
+ that You distribute, all copyright, patent, trademark, and
107
+ attribution notices from the Source form of the Work,
108
+ excluding those notices that do not pertain to any part of
109
+ the Derivative Works; and
110
+
111
+ (d) If the Work includes a "NOTICE" text file as part of its
112
+ distribution, then any Derivative Works that You distribute must
113
+ include a readable copy of the attribution notices contained
114
+ within such NOTICE file, excluding those notices that do not
115
+ pertain to any part of the Derivative Works, in at least one
116
+ of the following places: within a NOTICE text file distributed
117
+ as part of the Derivative Works; within the Source form or
118
+ documentation, if provided along with the Derivative Works; or,
119
+ within a display generated by the Derivative Works, if and
120
+ wherever such third-party notices normally appear. The contents
121
+ of the NOTICE file are for informational purposes only and
122
+ do not modify the License. You may add Your own attribution
123
+ notices within Derivative Works that You distribute, alongside
124
+ or as an addendum to the NOTICE text from the Work, provided
125
+ that such additional attribution notices cannot be construed
126
+ as modifying the License.
127
+
128
+ You may add Your own copyright statement to Your modifications and
129
+ may provide additional or different license terms and conditions
130
+ for use, reproduction, or distribution of Your modifications, or
131
+ for any such Derivative Works as a whole, provided Your use,
132
+ reproduction, and distribution of the Work otherwise complies with
133
+ the conditions stated in this License.
134
+
135
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
136
+ any Contribution intentionally submitted for inclusion in the Work
137
+ by You to the Licensor shall be under the terms and conditions of
138
+ this License, without any additional terms or conditions.
139
+ Notwithstanding the above, nothing herein shall supersede or modify
140
+ the terms of any separate license agreement you may have executed
141
+ with Licensor regarding such Contributions.
142
+
143
+ 6. Trademarks. This License does not grant permission to use the trade
144
+ names, trademarks, service marks, or product names of the Licensor,
145
+ except as required for reasonable and customary use in describing the
146
+ origin of the Work and reproducing the content of the NOTICE file.
147
+
148
+ 7. Disclaimer of Warranty. Unless required by applicable law or
149
+ agreed to in writing, Licensor provides the Work (and each
150
+ Contributor provides its Contributions) on an "AS IS" BASIS,
151
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
152
+ implied, including, without limitation, any warranties or conditions
153
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
154
+ PARTICULAR PURPOSE. You are solely responsible for determining the
155
+ appropriateness of using or redistributing the Work and assume any
156
+ risks associated with Your exercise of permissions under this License.
157
+
158
+ 8. Limitation of Liability. In no event and under no legal theory,
159
+ whether in tort (including negligence), contract, or otherwise,
160
+ unless required by applicable law (such as deliberate and grossly
161
+ negligent acts) or agreed to in writing, shall any Contributor be
162
+ liable to You for damages, including any direct, indirect, special,
163
+ incidental, or consequential damages of any character arising as a
164
+ result of this License or out of the use or inability to use the
165
+ Work (including but not limited to damages for loss of goodwill,
166
+ work stoppage, computer failure or malfunction, or any and all
167
+ other commercial damages or losses), even if such Contributor
168
+ has been advised of the possibility of such damages.
169
+
170
+ 9. Accepting Warranty or Additional Liability. While redistributing
171
+ the Work or Derivative Works thereof, You may choose to offer,
172
+ and charge a fee for, acceptance of support, warranty, indemnity,
173
+ or other liability obligations and/or rights consistent with this
174
+ License. However, in accepting such obligations, You may act only
175
+ on Your own behalf and on Your sole responsibility, not on behalf
176
+ of any other Contributor, and only if You agree to indemnify,
177
+ defend, and hold each Contributor harmless for any liability
178
+ incurred by, or claims asserted against, such Contributor by reason
179
+ of your accepting any such warranty or additional liability.
180
+
181
+ END OF TERMS AND CONDITIONS
182
+
183
+ APPENDIX: How to apply the Apache License to your work.
184
+
185
+ To apply the Apache License to your work, attach the following
186
+ boilerplate notice, with the fields enclosed by brackets "[]"
187
+ replaced with your own identifying information. (Don't include
188
+ the brackets!) The text should be enclosed in the appropriate
189
+ comment syntax for the file format. We also recommend that a
190
+ file or class name and description of purpose be included on the
191
+ same "printed page" as the copyright notice for easier
192
+ identification within third-party archives.
193
+
194
+ Copyright 2025 Justin Joyce (@joocer)
195
+
196
+ Licensed under the Apache License, Version 2.0 (the "License");
197
+ you may not use this file except in compliance with the License.
198
+ You may obtain a copy of the License at
199
+
200
+ http://www.apache.org/licenses/LICENSE-2.0
201
+
202
+ Unless required by applicable law or agreed to in writing, software
203
+ distributed under the License is distributed on an "AS IS" BASIS,
204
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
205
+ See the License for the specific language governing permissions and
206
+ limitations under the License.
207
+ Project-URL: Homepage, https://github.com/mabel-dev/opteryx-shared-services
208
+ Keywords: opteryx,config,logging,preflight,healthcheck
209
+ Classifier: Development Status :: 4 - Beta
210
+ Classifier: Intended Audience :: Developers
211
+ Classifier: License :: OSI Approved :: MIT License
212
+ Classifier: Programming Language :: Python :: 3
213
+ Classifier: Programming Language :: Python :: 3 :: Only
214
+ Classifier: Programming Language :: Python :: 3.11
215
+ Classifier: Programming Language :: Python :: 3.12
216
+ Classifier: Programming Language :: Python :: 3.13
217
+ Classifier: Operating System :: OS Independent
218
+ Requires-Python: >=3.11
219
+ Description-Content-Type: text/markdown
220
+ License-File: LICENSE
221
+ Requires-Dist: google-cloud-firestore==2.*
222
+ Provides-Extra: storage
223
+ Requires-Dist: google-cloud-storage==3.*; extra == "storage"
224
+ Provides-Extra: secrets
225
+ Requires-Dist: google-cloud-secret-manager==2.*; extra == "secrets"
226
+ Provides-Extra: test
227
+ Requires-Dist: pytest; extra == "test"
228
+ Dynamic: license-file
229
+
230
+ # opteryx-shared-services
231
+
232
+ Capabilities every Opteryx service needs, in one package.
233
+
234
+ ```bash
235
+ pip install opteryx-shared-services
236
+ ```
237
+
238
+ Three seed capabilities, each of which was previously copied into eight service
239
+ repos and had silently diverged there:
240
+
241
+ | module | provides |
242
+ | --- | --- |
243
+ | `opteryx_shared_services.config` | the platform configuration client |
244
+ | `opteryx_shared_services.logging` | structured logging, and the audit wire format the fleet's log ingestion selects on |
245
+ | `opteryx_shared_services.preflight` | startup dependency checks that fail a Cloud Run revision rather than letting an instance that cannot serve replace one that can |
246
+
247
+ Nothing is imported by the top-level package. A service that needs only
248
+ configuration must not pay for a Firestore, GCS or Secret Manager import it
249
+ never uses, so each capability is imported by name.
250
+
251
+ ## Why a package, not vendored copies
252
+
253
+ The previous mechanism was copy-by-`vendor.sh`. It does not hold. At the point
254
+ this package was created, `config_client.py` existed in **four different
255
+ versions** across eight repos, and **five of the eight** were missing
256
+ `promote_to_environ` — the function that copies the configuration document into
257
+ `os.environ`, which is the only way `opteryx.config` and `opteryx_catalog` (both
258
+ of which read `os.environ` directly) ever see it. One repo had been re-vendored
259
+ two days earlier and *still* lacked it, because it was synced from a stale
260
+ checkout.
261
+
262
+ Nothing could detect that, because a copy carries no version. A pinned
263
+ dependency answers "which version is this service on?" by reading
264
+ `pyproject.toml`.
265
+
266
+ ## `config`
267
+
268
+ ```python
269
+ from opteryx_shared_services.config import get_config
270
+
271
+ AUTH_URL = get_config("AUTH_URL", default="https://authenticate.opteryx.app")
272
+ ```
273
+
274
+ Configuration lives in Firestore at `(default)/config/<environment>`, one
275
+ document per environment. Resolution order is process environment → the
276
+ configuration document → the caller's default, so a value set in the service's
277
+ ENVVARs always wins.
278
+
279
+ The document is read once at import and every value copied into `os.environ`
280
+ without overwriting anything already there — that is what reaches code which
281
+ cannot call `get_config` (`opteryx.config`, `opteryx_catalog`). The client is
282
+ deliberately fail-open: if Firestore is unreachable it serves last-known values
283
+ and otherwise the caller's default, so a Firestore blip cannot take down the
284
+ fleet.
285
+
286
+ `OPTERYX_CONFIG_EAGER=false` skips the read at import;
287
+ `OPTERYX_CONFIG_PROMOTE=false` skips the copy into `os.environ`.
288
+
289
+ ## `logging`
290
+
291
+ ```python
292
+ from opteryx_shared_services.logging import get_logger, set_log_name
293
+
294
+ set_log_name("opteryx.worker")
295
+ logger = get_logger()
296
+ ```
297
+
298
+ **The audit wire format is a cross-service contract.** `xb500.opteryx`'s
299
+ `transform_audit_logs` ingests Cloud Logging entries whose
300
+ `jsonPayload.severity` is `"AUDIT"` into `ops.audit_log`;
301
+ `transform_billing_logs` selects `"BILLING"` the same way. That imposes three
302
+ requirements on every `logger.audit(...)` call:
303
+
304
+ 1. the line must be **valid JSON on its own** — Cloud Logging only parses a
305
+ stdout line into `jsonPayload` when the whole line is JSON, so a
306
+ `time | LEVEL | name | {...}` prefix makes it opaque `textPayload`;
307
+ 2. the payload must carry **`severity` itself** — the LogEntry's GCP-assigned
308
+ severity is not what the transform selects on;
309
+ 3. a caller-supplied severity must **survive verbatim** — billing events pass
310
+ `severity="BILLING"` and are ingested by a different transform.
311
+
312
+ So audit and alert records get their own stdout handler with no formatter
313
+ prefix, and their payload is passed through untouched. Ordinary records go to a
314
+ separate handler that never sees them.
315
+
316
+ Ordinary records are JSON with a mapped `severity` under `K_SERVICE` (every
317
+ Cloud Run deployment), because formatted text lands as `textPayload` at DEFAULT
318
+ severity where severity-based alerting cannot see even an ERROR. Everywhere else
319
+ they stay human-readable. `LOG_FORMAT=json` / `LOG_FORMAT=text` overrides either
320
+ way.
321
+
322
+ Also included: `set_trace_context()` for request correlation, `extra=` fields
323
+ riding along as their own `jsonPayload` fields, tracebacks folded into `message`
324
+ so Error Reporting groups them, `propagate = False` so uvicorn does not
325
+ duplicate every line, and third-party loggers (`opteryx.config_client`,
326
+ `opteryx_catalog`) adopted at WARNING so a broken alert sink cannot present as
327
+ a channel simply being quiet.
328
+
329
+ ### What this fixed
330
+
331
+ At the point of consolidation, five of eight services emitted audit records the
332
+ audit pipeline could not see:
333
+
334
+ | service | was | now |
335
+ | --- | --- | --- |
336
+ | control, register | correct | unchanged |
337
+ | xb500 | bypassed logging via `opteryx_catalog.audit` | either route works |
338
+ | worker | JSON, but AUDIT mapped to severity `"NOTICE"` | `"AUDIT"` |
339
+ | jobs, upload, authenticate | text formatter → `textPayload` | raw JSON on stdout |
340
+ | odata | no handler at all → root logger | raw JSON on stdout |
341
+
342
+ Adopting this module therefore **starts new records flowing** into
343
+ `ops.audit_log` from five services. Validate their payloads against
344
+ `AUDIT_LOG_SCHEMA` before rolling out.
345
+
346
+ ## `preflight`
347
+
348
+ Each service keeps a small `app/preflight.py` that declares what it needs:
349
+
350
+ ```python
351
+ import sys
352
+
353
+ from opteryx_shared_services.preflight import Preflight
354
+ from opteryx_shared_services.preflight import firestore_read
355
+ from opteryx_shared_services.preflight import gcs_list
356
+ from opteryx_shared_services.preflight import gcs_write
357
+ from opteryx_shared_services.preflight import secret_manager
358
+
359
+ preflight = Preflight(
360
+ component="worker",
361
+ checks=(
362
+ secret_manager(),
363
+ firestore_read("firestore-jobs", collection="jobs"),
364
+ firestore_read(
365
+ "firestore-catalog",
366
+ collection="$catalog",
367
+ database_key="FIRESTORE_DATABASE",
368
+ covered_by="firestore-jobs",
369
+ ),
370
+ gcs_list("gcs-data", bucket_key="GCS_BUCKET"),
371
+ gcs_write("gcs-results", bucket_key="RESULTS_BUCKET"),
372
+ ),
373
+ )
374
+
375
+ if __name__ == "__main__":
376
+ sys.exit(preflight.main())
377
+ ```
378
+
379
+ Then run it *before* the server, with `&&` so a non-zero preflight means the
380
+ server is never `exec`'d:
381
+
382
+ ```dockerfile
383
+ CMD python -m app.preflight && exec python -m uvicorn app.main:service --host 0.0.0.0 --port ${PORT:-8080}
384
+ ```
385
+
386
+ `app/main.py`'s lifespan calls `preflight.run_startup_checks()`; the health route
387
+ calls `preflight.readiness()` and answers 503 when it is false. Keep
388
+ `/health/live` as a separate dependency-free ping, so a transient Firestore blip
389
+ does not get a busy instance killed mid-request.
390
+
391
+ ### Why a separate process, not just the ASGI lifespan
392
+
393
+ A container running `uvicorn --workers N` has a supervisor that binds the
394
+ listening socket in the **parent** and respawns any child that dies. A lifespan
395
+ that raises kills one child, the parent starts another, and the port stays open
396
+ throughout — the revision looks alive while no worker can serve a thing.
397
+
398
+ `python -m app.preflight` runs before uvicorn exists. Its exit code is what fails
399
+ the revision. Keep the lifespan check too, as a second line of defence, but it is
400
+ not what makes the container fail.
401
+
402
+ ### Probe builders
403
+
404
+ | builder | proves | use for |
405
+ | --- | --- | --- |
406
+ | `secret_manager(name=…, secret_key=…)` | Secret Manager reachable; reads a named secret when one is configured | any service that resolves secrets |
407
+ | `firestore_read(name, collection=…, database_key=…, covered_by=…)` | a collection is readable | every Firestore-backed service |
408
+ | `gcs_list(name, bucket_key=…)` | a bucket is listable | buckets the service **reads** |
409
+ | `gcs_write(name, bucket_key=…)` | an object can be created (and is then removed) | buckets the service **writes** |
410
+ | `custom(name, body)` | whatever `body` returns a `CheckResult` for | Cloud Tasks queues, Valkey, another service's `/health` |
411
+
412
+ Builders take **configuration keys**, not values. The name is resolved when the
413
+ probe runs, because configuration is promoted into `os.environ` during startup —
414
+ a value captured at import can be older than the one the rest of the process is
415
+ using.
416
+
417
+ **Declare the direction the service uses, not both.** A LIST is not a substitute
418
+ for a CREATE and vice versa: a service account holding `objectCreator` on a
419
+ results bucket (enough to serve every request) fails a read probe, and one
420
+ holding only `objectViewer` sails through a read probe and then fails at the
421
+ first upload. `bucket.exists()` is worse than either — it needs
422
+ `storage.buckets.get`, which `objectViewer` does not carry.
423
+
424
+ ### Cost and safety
425
+
426
+ Probes make real RPCs, one of them a write, and `/health` is usually
427
+ unauthenticated — so results are cached for 30 seconds. Without that the endpoint
428
+ would be a way to bill the project by curl loop. Alerts are raised only when the
429
+ probes actually run, so a cached failure does not re-report.
430
+
431
+ Each probe is bounded at 5s and the whole set at 15s — the latter because a
432
+ client that hangs *before* it makes an RPC (ADC discovery, metadata server) never
433
+ reaches the per-call timeout. The write probe puts its object under
434
+ `_healthcheck/`, so a bucket lifecycle rule can mop up if the service account
435
+ cannot delete what it creates.
436
+
437
+ `HEALTH_DEPENDENCY_CHECKS=false` turns the probes off everywhere — both the
438
+ startup gate and `/health`. It is for running a service somewhere its
439
+ dependencies genuinely are not reachable (a laptop, a unit test), not a way to
440
+ keep a broken deployment serving.
441
+
442
+ ## Optional extras
443
+
444
+ Only the config client's Firestore dependency is unconditional. The preflight
445
+ probes import their clients lazily, inside the probe that needs them:
446
+
447
+ ```bash
448
+ pip install "opteryx-shared-services[storage,secrets]"
449
+ ```
450
+
451
+ ## Releasing
452
+
453
+ Tag `version-<pyproject version>`. The workflow gates on the full test matrix
454
+ (3.11–3.14) and refuses a tag that does not match `pyproject.toml`.
455
+
456
+ ## Tests
457
+
458
+ ```bash
459
+ python -m pip install -e ".[test,storage,secrets]"
460
+ python -m pytest tests -q
461
+ ```