dohertj2/scadaproj
1
0
Fork 0
Code Issues 16 Pull Requests Actions Packages Projects Releases Wiki Activity

[ignitionoee] Move the OeeRouter secrets store before deploying 2b8ff324 (Secrets 0.6.2 refuses the in-install path) #21

New Issue
Open
opened 2026-11-06 15:54:01 -05:00 by dohertj2 · 0 comments
dohertj2 commented 2026-11-06 15:54:01 -05:00
Owner
Copy Link
Copy Source

ignitionoee main is now 2b8ff324 (#7), with Secrets 0.6.2 and Auth 0.3.0. The box's own appsettings.json on IGNTN-INT-VP01 still sets Secrets:SqlitePath=data/oee-secrets.db. The new build refuses to start until the store is moved; no data is lost.

  1. Stop OeeRouter.
  2. Move F:\apps\ignitionrouter\data\oee-secrets.db, plus any -wal/-shm files, to a folder outside F:\apps\ignitionrouter.
  3. Either set Secrets__SqlitePath to that absolute path in the service's Environment, or remove the key so the router uses the ProgramData default (%ProgramData%\ZB.MOM.Oee\oee-secrets.db). The service account needs write access to the folder.
  4. Swap in the build and start the service.

Related: data/oee-inbound-api-keys.sqlite (the inbound API-key store) also lives inside the install folder, which was the cause of the 2026-09-23 401s. Consider moving it out the same way.

ignitionoee `main` is now `2b8ff324` (#7), with Secrets 0.6.2 and Auth 0.3.0. The box's own `appsettings.json` on IGNTN-INT-VP01 still sets `Secrets:SqlitePath=data/oee-secrets.db`. **The new build refuses to start** until the store is moved; no data is lost. 1. Stop `OeeRouter`. 2. Move `F:\apps\ignitionrouter\data\oee-secrets.db`, plus any `-wal`/`-shm` files, to a folder outside `F:\apps\ignitionrouter`. 3. Either set `Secrets__SqlitePath` to that absolute path in the service's Environment, or remove the key so the router uses the ProgramData default (`%ProgramData%\ZB.MOM.Oee\oee-secrets.db`). The service account needs write access to the folder. 4. Swap in the build and start the service. Related: `data/oee-inbound-api-keys.sqlite` (the inbound API-key store) also lives inside the install folder, which was the cause of the 2026-09-23 401s. Consider moving it out the same way.
dohertj2 added the type:deploy-gatepriority:p1cross-repo labels 2026-11-06 15:54:01 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked
Blocked by dependency or external hold
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label cross-repo priority:p1 type:deploy-gate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/scadaproj#21
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?