Allow/disallow service integration inheritance
Problem to solve
As part of &2137, we want to be able to allow/disallow service integration inheritance.
I can see requirements that could be in conflict, project-level or group-level settings can see the inherited values but group-level or instance-level settings can mask the values that are going to be propagated to the lower levels.
As a project owner with a project owner overriding inherited settings, I want those overrides clearly labeled and the original value displayed, so that it's clear what I'm overriding and what the overridden value was.
The Group-level integration can mask individual values. On a per-field basis, the Group-level configuration can be set to mask any values, preventing projects inheriting those settings from viewing the value directly in the UI or API.
Further details
As part of this issue, we have to investigate how we are going to solve the problem. Then we will be able to create the appropriate backend and frontend issues.
As a Minimum Viable Change, I think we should not be able to override/mask individual values but the whole configuration.
Proposal
Permissions and Security
Documentation
- Documentation will be needed that clearly explains how this feature works and what is allowed/disallowed in either state.