brainzlab 0.1.34 → 0.1.36
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.
- checksums.yaml +4 -4
- data/CHANGELOG.md +6 -0
- data/lib/brainzlab/flux/client.rb +1 -1
- data/lib/brainzlab/instrumentation/aws.rb +10 -7
- data/lib/brainzlab/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 4ff0306e7d8fe78a37efbc84090d9ffc65dbfa46f76f5ada564304368a5d218a
|
|
4
|
+
data.tar.gz: 79ab8e0b681d14468a6cd24577c3850bd0ce0800d547bc7bb5020ff69cb40054
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: cdb11db4fd944c0978bedf6e619061269e21c334a036bfb3d5d4b7d3d9c9f50317e87434d8915e5adfefc8d6f2c37f9da3cf75dfefd7776eb1edc6f90ad0b818
|
|
7
|
+
data.tar.gz: eecd6d8197389329c70971e93fc9d2cbede53eea1866e181182a1c38f5d8f273585e44c071c440cb495f03e822928ed7dd8d6ffd527791022ba31b05760e8016
|
data/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,12 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
|
4
4
|
|
|
5
|
+
## [0.1.36] - 2026-10-29
|
|
6
|
+
|
|
7
|
+
### Fixed
|
|
8
|
+
|
|
9
|
+
- **Flux client now falls back to `secret_key`.** `Flux::Client#api_key` only read `flux_ingest_key || flux_api_key`, while `Configuration#flux_valid?` also accepted `secret_key`. Apps configured with only `BRAINZLAB_SECRET_KEY` (no `FLUX_API_KEY` / `FLUX_INGEST_KEY`) therefore sent `Authorization: Bearer ` with an empty token, and Flux rejected every batch with 401. The client now uses `Configuration#flux_auth_key` (`flux_ingest_key || flux_api_key || secret_key`), matching how Pulse resolves its key. Measured in production on 2026-10-29: every `solid_queue.job.duration_ms` batch from services on 0.1.32/0.1.33 without a Flux-specific key was rejected.
|
|
10
|
+
|
|
5
11
|
## [0.1.31] - 2026-06-18
|
|
6
12
|
|
|
7
13
|
### Fixed
|
|
@@ -15,13 +15,16 @@ module BrainzLab
|
|
|
15
15
|
private
|
|
16
16
|
|
|
17
17
|
def install_plugin!
|
|
18
|
-
# AWS
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
#
|
|
18
|
+
# Registered through Seahorse only. Every AWS client inherits from
|
|
19
|
+
# Seahorse::Client::Base, so this one hook covers S3, SQS and the rest,
|
|
20
|
+
# on every version of the SDK.
|
|
21
|
+
#
|
|
22
|
+
# There used to be a second registration through Aws.config[:plugins].
|
|
23
|
+
# That option only exists on newer aws-sdk-core; on older ones it does
|
|
24
|
+
# not degrade, it makes *every* client fail to construct with
|
|
25
|
+
# "invalid configuration option :plugins" — so an app pinned to an
|
|
26
|
+
# older SDK could not talk to S3 at all. It bought nothing either way,
|
|
27
|
+
# since the handler below is the same handler.
|
|
25
28
|
return unless defined?(::Seahorse::Client::Base)
|
|
26
29
|
|
|
27
30
|
install_seahorse_handler!
|
data/lib/brainzlab/version.rb
CHANGED