zqr10159 commented on PR #4294:
URL: https://github.com/apache/hertzbeat/pull/4294#issuecomment-5138496266
Addressed the remaining standalone Collector bootstrap blocker on head
`e533b4e106`.
The installation contract now provisions two independent values to Manager
and
every standalone Collector:
- `COMMON_SECRET`, generated with `openssl rand -hex 16`, yielding a valid
32-byte AES key;
- `CLUSTER_AUTH_ACTIVE_SECRET`, independently generated with
`openssl rand -hex 32`.
The 64-character authentication output is explicitly not reused as
`COMMON_SECRET`. All five Compose definitions require both variables, all
five
packaged application configurations map `COMMON_SECRET` to `common.secret`,
and the root/localized quick starts plus Docker, Compose, package, native
Collector, Collector-reference, and upgrade guides describe the same
contract.
The upgrade path preserves an existing AES key rather than replacing it and
risking unreadable encrypted data.
Regression and runtime proof:
- the new packaging contract failed on the reviewed head because Compose and
documentation omitted `COMMON_SECRET`;
- the updated 22-module packaging/authentication reactor passed;
- `CollectorDocumentedEnvironmentIntegrationTest` launches a separate real
Collector JVM with both documented variables and verifies stable startup;
- a rebuilt and extracted `apache-hertzbeat-collector-1.9.0-bin.tar.gz` was
started with the same environment, reached `Started Collector`, and
remained
alive without a common-secret validation error;
- all five Compose definitions rendered successfully;
- the 24-module startup package and 24-module release-profile assembly
passed;
- the generated Compose archive retains both requirements in all five
distributions.
The temporary package extraction and source-tree test logs were removed after
verification. GitHub CI is now running on the amended head.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
