Full Changelog 1.0.3

Released 2026-09-04 · v7.1.2.a · 3 issues · 4 fixes

The complete record: every commit in the release, grouped by type, including work that never reaches a customer-facing note. The external changelog is the readable summary of the same release.

Jira References

  • DEV-1933 - Angular Project > USP > No Mesh > Client via Wi-Fi > Wi-Fi management plus > "Network topology" cube > Incorrect "RSSI" value

  • DEV-2281 - Angular Project > TR-181 > Wi-Fi management plus > Dataelement / MultiAP > Network connected clients > Client with "Undefined" status is absent

  • DEV-2551 - Angular project > Support portal > Wi-Fi management plus > Gateway Wi-Fi status cube > A false warning

Bug Fixes

  • Fix

  • DEV-2281 - Angular Project > TR-181 > Wi-Fi management plus > Dataelement / MultiAP > Network connected clients > Client with "Undefined" status is absent

  • DEV-1933 - Angular Project > USP > No Mesh > Client via Wi-Fi > Wi-Fi management plus > "Network topology" cube > Incorrect "RSSI" value

  • DEV-2551 - Angular project > Support portal > Wi-Fi management plus > Gateway Wi-Fi status cube > A false warning

Documentation

  • Restructure to phase-based skeleton

    Rewrite installation.adoc as the canonical Docker Compose deployment guide for FT Device Network Service, matching the FTACS reference Auth, Offline Servers, Preparation, Deployment, Verification, Port Reference, Stack Management, Production Checklist, Troubleshooting.

    Corrects several stale facts inherited from the pre-Docker manual-JAR the native TCP port (9000); the ClickHouse schema is created automatically by Flyway on startup, not via manual SQL; the Hazelcast client config is baked into the image (only HZ_MEMBERS is overridable, not an external file via HZ_CONFIG_PATH); FTACS and an optional MQTT broker are documented as real dependencies of the ingestion pipeline.

    separate-host-deployment.adoc is trimmed to a short architecture/diagram page that points to installation.adoc for the actual procedure, instead of carrying a second, diverging deployment story. nav.adoc and index.adoc are updated to match.

  • Correct ClickHouse table list and soften multi-arch claim

    • Flyway creates nine network_* tables, not seven; verification step listed network_issue_type (does not exist) — real table is network_issue. Names taken from db/changelog migrations, not the stale database.adoc.

    • Fix the same stale network_issue_type name in database.adoc DDL.

    • Offline: do not assert the :latest manifest is multi-arch; the CI publish path defaults to amd64, so document how to verify the manifest and the arm64 fallback.

  • Update antora version to 1.0.3 (dev)

  • Regenerate changelog for release 1.0.2

  • Unify structure, dependencies table and ClickHouse 26.2

  • Fix cross-references and residual consistency findings

  • Correct environment and mount facts

  • Drop document-level anchors from cross-references

    Asciidoctor does not emit an element id for an anchor placed above the document title, so these fragments never resolved in the built HTML. Linking the page has identical behaviour.

  • Document host.docker.internal for peers outside Docker

    Matches the UI Backend guide: peers running on the same host but outside Docker are unreachable as localhost from inside the container.

  • Align Registry Authentication with the reference format

  • Use the platform directory layout

    The full-system deployment guide defines one directory per service directly under /usr/local/ft-system. Neither the ft-data level nor the ft-services root exists there; the divergence from the shipped compose and .env is recorded in docs/decisions/LOG.md.

  • Document the platform directory layout and env file split

  • Add the missing Directory Layout anchor

  • Fix defects found in the documentation audit

  • Move device-network module to OneIot Web services topic and refactor guide details

  • Update antora version to 1.0.3

  • Add changelog for release 1.0.3

  • Update antora version to 1.0.4 (dev)

Chores

  • Update docs

  • Add deployment.yaml contract for Deployment Manager

    Deployment Manager reads this file from the tip of this branch to know the service’s image, ports, volumes, clustering pattern and the variables an operator must fill in. It was previously vendored in ft-internal-tools (deployment-manager/catalogue/contracts/ft-device-network-service.yaml); this repository now owns it.

  • Add the deployment/ config tree Deployment Manager mounts

    These are the application config files a generated Compose bundle mounts into this service’s container. They were vendored in ft-internal-tools (deployment-manager/catalogue/services/); this repository now owns them, and Deployment Manager reads them from the tip of this branch.

    Private key material is deliberately NOT here: keys and keystores stay in the one place they already live and are laid over this tree at generation time, so the same private key does not gain a copy per repository.

CI

  • Add manual Gradle cache cleanup job for the self-hosted runner

  • Run the build summary job on the self-hosted runner

Docker Images

ft-device-network-service

Image

hub.friendly-tech.com/ftacs/ft-device-network-service:v1.0.3-b0.0.1

SHA256

sha256:c3299382b8bfde81dd39e6a59161d3df6143d350b2b07a1cb81d8eca2bb72218

Pull from Registry

docker pull hub.friendly-tech.com/ftacs/ft-device-network-service:v1.0.3-b0.0.1

Download for Offline Use

docker pull hub.friendly-tech.com/ftacs/ft-device-network-service:v1.0.3-b0.0.1
docker save hub.friendly-tech.com/ftacs/ft-device-network-service:v1.0.3-b0.0.1 -o ft-device-network-service-v1.0.3-b0.0.1.tar

gzip ft-device-network-service-v1.0.3-b0.0.1.tar

Load on Closed Network

gunzip ft-device-network-service-v1.0.3-b0.0.1.tar.gz
docker load -i ft-device-network-service-v1.0.3-b0.0.1.tar

Dependencies

  • ACS → FT Configs Service v1.0.2-b0.0.1

  • UI Backend → ACS v7.1.2-b0.0.1

  • UI Portals → UI Backend v7.1.2-b0.0.1

  • FT Device Network → ACS v7.1.2-b0.0.1

  • UI AI Agent → UI Backend v7.1.2-b0.0.1

  • UI AI Agent → FT Device Network v1.0.3-b0.0.1

See also