mirror of
https://github.com/andwati/zitadel.git
synced 2026-11-15 02:15:14 +00:00
chore: rename configuration to settings (#11568)
# Which Problems Are Solved naming inconsistencies: Configuration <-> Settings # How the Problems Are Solved # Additional Changes # Additional Context - Closes #11282
This commit is contained in:
@@ -14,7 +14,7 @@ This advisory applies to self-hosted ZITADEL installations with custom roles to
|
||||
|
||||
## Description
|
||||
|
||||
In upcoming ZITADEL versions, RBAC also applies to [system users defined in the ZITADEL runtime configuration](/guides/integrate/zitadel-apis/access-zitadel-system-api#runtime-configuration).
|
||||
In upcoming ZITADEL versions, RBAC also applies to [system users defined in the ZITADEL runtime configuration](/guides/integrate/zitadel-apis/access-zitadel-system-api#runtime-settings).
|
||||
This enables fine-grained access control to the system API as well as other APIs for system users.
|
||||
ZITADEL defines the new default roles *SYSTEM_OWNER* and *SYSTEM_OWNER_VIEWER*.
|
||||
System users without any memberships defined in the configuration will be assigned the *SYSTEM_OWNER* role.
|
||||
|
||||
@@ -23,7 +23,7 @@ This new feature adds the following fields to the `setup` configuration, previou
|
||||
- `Telemetry`
|
||||
- `SystemAPIUsers`
|
||||
|
||||
If you use different configurations on `setup` and `start` and have overwritten previously mentioned configurations please make sure to also add them to the configuration provided to ZITADEL `setup` command.
|
||||
If you use different settings on `setup` and `start` and have overwritten previously mentioned settings please make sure to also add them to the configuration provided to ZITADEL `setup` command.
|
||||
|
||||
## Statement
|
||||
|
||||
|
||||
Reference in New Issue
Block a user