Sven laptop
635a130f0b
Build and Push Docker Images / detect-changes (push) Successful in 11s
Build and Push Docker Images / build-auth-api (push) Successful in 1m0s
Build and Push Docker Images / build-employee-api (push) Successful in 1m2s
Build and Push Docker Images / build-transit-api (push) Successful in 1m1s
Build and Push Docker Images / build-error-log-api (push) Successful in 1m5s
Build and Push Docker Images / build-admin-ui (push) Successful in 1m13s
Build and Push Docker Images / build-monitoring-ui (push) Successful in 1m15s
Build and Push Docker Images / deploy-test-node (push) Successful in 3s
### Summary of Changes
1. Documentation Consolidation:
• Relocated the docs/ folder and all repository .md files (README.md, DEPLOYMENT.md, DOCKER_README.md,
DOMAINS_README.md, GETTING_STARTED.md, CI_CD_PORTAINER_GUIDE.md, ADMIN_DEPLOYMENT_SUMMARY.md,
SECURITY_PRIVATE_FILES.md, handoff.md, azure-project-plan.md, plus service-specific READMEs) into .
• Updated document links in README.md.
2. AI Agent Project Map:
• Created PROJECT_MAP.md in the project root containing complete architecture diagrams, service specs, ports, DB
schemas, environment variables, and developer workflows.
• Added PROJECT_MAP.md to .gitignore.
3. Monitoring UI & Infrastructure Integration:
• Added monitoring_ui service to docker-compose.yml (port 5175).
• Configured Gitea workflow docker-build.yml for monitoring_ui builds.
• Added CORS middleware headers in index.js.
• Added nginx.conf copy step in Dockerfile.
──────
### Recommended Commit Message
docs: consolidate project documentation into monitoring_ui and add agent project map
- Move all markdown documentation files and docs/ folder into monitoring_ui/docs/
- Update documentation hub index (monitoring_ui/docs/README.md) with relative paths
- Generate comprehensive AI agent reference map (PROJECT_MAP.md) in repository root
- Add PROJECT_MAP.md and monitoring_ui build output/env overrides to .gitignore
- Integrate monitoring_ui service into docker-compose.yml and Gitea CI workflow
- Configure CORS handling in employee_api for monitoring dashboard access
──────
### Alternative Short Commit Message
refactor(docs): move docs to monitoring_ui and create AI agent PROJECT_MAP.md
2.5 KiB
2.5 KiB
Important: This skill provides guidance and recommended instructions to assist the AI system. Outputs are not guaranteed to be complete, correct, secure, or applicable to every scenario. Results should be reviewed and validated by a human before being applied. The AI model may choose not to follow all instructions exactly, and additional verification may be required.
Subscription Resolution — Defensive Fallback
The azure-app-onboard orchestrator resolves the subscription at Step 1 (login hard gate) and writes subscriptionId, subscriptionName, tenantId to context.json.azure before any phase runs. In normal operation, context.json.azure.subscriptionId is always set by the time prepare runs.
At prepare phase entry, verify context.json.azure.subscriptionId is set. If it is (expected path), use it — done.
If context.json.azure is somehow empty, resolve now rather than halting the flow:
- Check env vars — if
AZURE_SUBSCRIPTION_IDis set, use it directly (withAZURE_TENANT_IDif set). WritesubscriptionId,subscriptionName,tenantIdtocontext.json.azure, done. - Run
az account show—az account show --query "{id:id, name:name, tenantId:tenantId}" -o json. If it succeeds, auto-select — writesubscriptionId,subscriptionName,tenantIdtocontext.json.azure. Do NOT runaz account listor present a picker. - Fallback:
mcp_azure_mcp_subscription_list+ picker — only ifaz account showfails. Callmcp_azure_mcp_subscription_listto retrieve all subscriptions (returnssubscriptionId,displayName,isDefault).- 1 subscription → auto-select, no question. Write
subscriptionId,subscriptionName,tenantIdtocontext.json.azure. - 2+ subscriptions → present a picker via
ask_user: list each subscription as a choice"{displayName} ({subscriptionId})"with the default marked. The user selects one. WritesubscriptionId,subscriptionName,tenantIdtocontext.json.azure.
- 1 subscription → auto-select, no question. Write
- MCP tool fails → attempt
az login(interactive browser login). If that fails (no browser, remote session), fall back toaz login --use-device-code. On success, retry from step 2. Cap login at 3 attempts total — if login still fails after the 3rd attempt, HALT once with a clear, actionable message: the exactaz login --tenant <tenant>command to run, and that re-invoking the agent resumes this session (completed phases are preserved). Do NOT retry past 3 attempts, and do NOT proceed without a resolved subscription.