Full Changelog 1.0.2
Released 2026-09-04 · v7.1.2.a · 1 issue · 1 feature · 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-2332 - FT Configs > ACS > "config_custom_data.xml" > Configuration file missing
Features
-
Add Account Info Mapping management UI
CRUD over cust_device1 column mappings with XML import (dry-run preview) and export, built on the shared FeaturePageLayout/DataTable/ImportWizardDialog. The column field is gated to the server allow-list (GET /columns), offering only valid and unused columns; 2944/2947 errors surface inline and the column stays fixed on edit.
Bug Fixes
-
Move Dockerfiles to repo root to match build context
The CI build-callable workflow on main invokes the build with context '.' and dockerfile 'Dockerfile', resolving to ./Dockerfile, but the file lived in docker/. Move both Dockerfile and Dockerfile.simple to the repo root and update the release/qa workflow paths accordingly. COPY paths are context-relative and remain unchanged.
-
Default build-callable dockerfile to repo root
Align the reusable workflow default with main and the new file location. Previously the default was docker/Dockerfile while the file now lives at the repo root, causing the build to look for a non-existent path when the callable is resolved from this branch.
-
Fix email add on login page
-
Doc
Documentation
-
Update antora version to 1.0.2 (dev)
-
Regenerate changelog for release 1.0.1
-
Align FT Configs UI install guide with the canonical format
Restructure installation.adoc onto the platform-wide install-guide skeleton used by the other eleven service components: fixed H2 order, explicit anchors on every H2/H3, canonical table headers, and symptom-named Troubleshooting subsections instead of a generic "Common Issues" block.
The guide now documents the platform deployment (image hub.friendly-tech.com/configs/ft-configs-ui:latest, published 3001 → 80 and 3443 → 443, install root /usr/local/ft-system with ft-configs-ui/certs/, env_file .env + ft-configs-ui/.env) instead of the developer compose file; each divergence is recorded in docs/decisions/LOG.md. Adds the missing Registry Authentication, Offline Servers, Network Requirements, Verification and Directory Layout sections, and drops the VITE_APP_* build-time variables, which exist nowhere in the sources.
The siblings keep only what they own: docker-and-deploy.adoc and https-deployment.adoc now xref the install guide for the runtime config and environment variables. Fixes the nginx locations table, whose unescaped pipes inside regex cells dropped rows from the Antora build, corrects the /ready upstream path, removes the false HSTS claim and the paraphrased entrypoint output, and deletes the Next.js-era env-vars partial.
nav.adoc lists the new section structure with labels matching the headings.
-
Fold HTTPS into the install guide and flatten the build-run group
-
Pin docker image to explicit version instead of latest tag
-
Add changelog for 1.0.1 build 0.0.2
-
Update antora version to 1.0.2
-
Add changelog for release 1.0.2
Chores
-
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-configs-ui.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.
-
Bump version to 1.0.2
CI
-
Make gha cache export non-fatal
The GitHub Actions cache service can return transient 5xx/4xx HTML errors that fail the whole build at the cache export step. Add ignore-error=true so a cache-to failure no longer aborts the image build and push.
-
Drop unreachable GHA cache backend from image build
The GHA cache service returns an edge-proxy HTML 400 on the self-hosted runners; the failed export tears down the buildkit connection and fails the job after the image has already been pushed. ignore-error only covers the cache write, not the dropped gRPC stream. Build is ~45s uncached.
Docker Images
ft-configs-ui
- Image
-
hub.friendly-tech.com/configs/ft-configs-ui:v1.0.2-b0.0.1 - SHA256
-
sha256:6e7b8537ea41a0150a41c534874b40b5bab0732df92b3624dc2cd3242e1b0d76
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