8000 Fix GRC Solution installation and editing on Bifrost 2.0 by wilhil · Pull Request #4 · gobifrost/grc · GitHub
[go: up one dir, main page]

Skip to content

Fix GRC Solution installation and editing on Bifrost 2.0 - #4

Open
wilhil wants to merge 2 commits into
gobifrost:mainfrom
wilhil:main
Open

wilhil wants to merge 2 commits into
gobifrost:mainfrom
wilhil:main

Conversation

@wilhil
@wilhil wilhil commented Nov 21, 2026
Copy link
Copy Markdown

Changes

  • Remove the deprecated global_repo_access key from bifrost.solution.yaml. Bifrost 2.0 rejects it during repository installation with HTTP 422. The canonical allow_outbound_access: false and allow_inbound_access: true settings stay unchanged.
  • Use the Bifrost SDK’s useUser() hook for user identity and the GRC editing gate instead of reading legacy JWT claims. This restores New framework for authorized users while keeping the Auditor read-only. Use the existing organization directory for provider status and wait for it before updating the saved organization view. No backend policies or role assignments change.

Validation

  • Installed the Git-connected Solution on a Bifrost 2.0 test instance; both app bundles deployed. Synced the UI follow-up successfully.
  • Reproduced the missing New framework button in Edge before the update and opened the creation dialog after it. Did not submit the form.
  • Typecheck and 10 mocked identity and permission assertions passed. Python: 178 passed; the same date-sensitive policy campaign test fails on upstream main.

This has not been thoroughly tested beyond app launching and ability to add which I couldn't do with the previous patch.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0