feat(openfga): add the openFga block to the install config - #679
Merged
Conversation
One OpenFGA instance serves a whole installation, so in a multi-data-center
setup exactly one data center deploys and publishes it and the others only
point at it. That is an installation-level decision rather than a chart
detail, so operators express it in config.yaml:
codesphere:
openFga:
deploy: true
apiUrl: https://openfga.1.cs.example.com
expose:
enabled: true
host: openfga.1.cs.example.com
Validation rejects the combinations that cannot work: a data center that
does not deploy OpenFGA has nowhere to fall back to and must name the
instance it uses, an exposed one needs a host, and a data center cannot
expose an OpenFGA it does not deploy.
Nothing reads the block yet; deriving the pc-applications values from it
follows separately.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: Jona Neef <Jona.Neef.97@gmail.com>
NJona
force-pushed
the
jona/openfga-install-config
branch
from
August 12, 2026 11:16
5d4c44e to
c2bc728
Compare
NautiluX
reviewed
Aug 13, 2026
NautiluX
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One OpenFGA instance serves a whole installation, so in a multi-data-center setup exactly one data center deploys and publishes it and the others only point at it. That is an installation-level decision rather than a chart detail, so operators express it in config.yaml:
Validation rejects the combinations that cannot work: a data center that does not deploy OpenFGA has nowhere to fall back to and must name the instance it uses, an exposed one needs a host, and a data center cannot expose an OpenFGA it does not deploy.
Nothing reads the block yet; deriving the pc-applications values from it follows separately.