Skip to content

Deploy the Skra ports (PR #1) together with the workflow authorization fix #3

Open

Description

@MTG-Thomas

PR #1 moves the work merged in MTG-Thomas/bifrost-docs-solution (now archived) onto mtg:

  • tenant-scoped asset expiration tracking (docs_list_expirations, dashboard widget, opt-in date fields)
  • IT Glue attachment sign-in redirect detection

Each change also has its own branch based on main (feat/expiration-tracking, fix/itglue-attachment-sign-in-redirects), so it can be proposed upstream.

Steps:

  1. Merge Security hardening for Solution workflows (tracked privately) #2's fix and PR Port Skra expiration tracking and IT Glue sign-in redirect fix from personal fork #1 into mtg.
  2. Run bifrost solution sync bifrost-docs (the install follows mtg; nothing auto-syncs).
  3. Smoke-test the dashboard expirations widget as a non-admin Docs Reader. Platform admins bypass policies, so an admin test proves nothing.
  4. Propose the two feature branches upstream as separate PRs.

Activity

  1. added
    priority: nowDo first: security, cutover blockers, deploy hygiene
    from-skraPorted or harvested from the retired Skra app
    on Nov 16, 2026
  2. MTG-Thomas commented on Nov 16, 2026

    @MTG-Thomas
    MemberAuthor

    Update: GitOps release flow (decided 2026-11-16)

    How Bifrost updates a Git-connected install (verified in platform main source): every 6 hours it reads version: from bifrost.solution.yaml at the connected ref's latest commit. Git tags and GitHub Releases are not used. If that version is newer, it badges the install and emits solution.update_available. Nothing applies the update except a sync (bifrost solution sync or POST /api/solutions/{id}/sync).

    Conventions for this repo:

    • Version every deployable change on mtg with a PEP 440 local label: 0.1.3+mtg.1, 0.1.3+mtg.2, … When upstream releases 0.1.4, merge it and continue with 0.1.4+mtg.1. I verified the ordering with the same packaging library the platform uses: 0.1.3 < 0.1.3+mtg.1 < 0.1.3+mtg.2 < 0.1.4. CI enforces the bump on PRs into mtg.
    • Merging to mtg deploys. The Solution GitOps controller (being built) receives the GitHub push webhook and syncs installs that follow mtg. Subscribing to solution.update_available gives a 6-hourly reconcile backstop. Until the controller is live, run bifrost solution sync bifrost-docs after merging.
    • mtg is branch-protected: PR plus green CI required.

    PR #1 gets version: 0.1.3+mtg.1 once the #4 test fix lands, and still waits for #2.

  3. MTG-Thomas commented on Nov 16, 2026

    @MTG-Thomas
    MemberAuthor

    GitOps status (2026-11-16):

    Remaining in this issue: merge #2's fix plus #1, opt in via the controller PR, and smoke-test as a non-admin Reader.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    from-skraPorted or harvested from the retired Skra apppriority: nowDo first: security, cutover blockers, deploy hygiene

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions