zqr10159 commented on PR #4294:
URL: https://github.com/apache/hertzbeat/pull/4294#issuecomment-5138056872
Addressed the remaining default-install and upgrade blocker on head
`0d850535b1`.
What changed:
- all five shipped Docker Compose definitions now require
`CLUSTER_AUTH_ACTIVE_SECRET` during interpolation and return an actionable
error before container startup when it is absent;
- every corresponding `conf/application.yml` exposes the complete
authentication block;
- each English and Chinese distribution guide creates a private `.env` with
`openssl rand -hex 32`, requires the value to be preserved across upgrades,
and requires standalone Collectors to use the same value;
- root/localized quick starts plus Docker, Compose, package,
native-Collector,
Collector-reference, and upgrade documentation now describe generation,
sharing, backup, and optional-to-required rollout;
- a Manager regression proves the all-in-one default replaces and persists
its
known-default AES root before Netty authentication validation, then reuses
the same root after restart.
Regression proof:
- on the reviewed head, the packaging contract failed because the Compose
distributions did not require/document an install secret and the package
upgrade path was incomplete;
- after the change, all five definitions fail as expected when the variable
is
absent and all five render with a valid fixture under Docker Compose
v5.0.2.
Validation:
- remoting authentication/compatibility: 18 tests passed, including the
seven-combination old/new loopback matrix;
- Manager bootstrap and packaging contracts: 3 tests passed;
- startup source package: 24-module reactor passed;
- release profile: 24-module reactor passed and generated server, Docker, and
Docker Compose archives;
- the generated Compose archive preserves the required-secret expression in
all five definitions;
- Checkstyle, added-test CJK scan, and Git whitespace checks passed.
The branch remains exactly one commit above `master`. GitHub CI is 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]
