Update Azure integration config visibility

Signed-off-by: James Brooks <jamesbrooks@spotify.com>
This commit is contained in:
James Brooks
2026-03-02 15:02:32 +00:00
parent 32cb991728
commit 993a59840b
2 changed files with 8 additions and 2 deletions
+5
View File
@@ -0,0 +1,5 @@
---
'@backstage/integration': patch
---
Fixed Azure integration config schema visibility annotations to use per-field `@visibility secret` instead of `@deepVisibility secret` on parent objects, so that non-secret fields like `clientId`, `tenantId`, `organizations`, and `managedIdentityClientId` are no longer incorrectly marked as secret.
+3 -2
View File
@@ -54,13 +54,14 @@ export interface Config {
* If no organization matches the first credential without an organization is used.
*
* If no credentials are specified at all, either a default credential (for Azure DevOps) or anonymous access (for Azure DevOps Server) is used.
* @deepVisibility secret
*/
credentials?: {
organizations?: string[];
clientId?: string;
/** @visibility secret */
clientSecret?: string;
tenantId?: string;
/** @visibility secret */
personalAccessToken?: string;
managedIdentityClientId?: string;
}[];
@@ -111,7 +112,6 @@ export interface Config {
endpoint?: string;
/**
* Optional credential to use for Azure Active Directory authentication.
* @deepVisibility secret
*/
aadCredential?: {
/**
@@ -126,6 +126,7 @@ export interface Config {
/**
* The client secret for the Azure AD application.
* @visibility secret
*/
clientSecret: string;
};