adding new setters for client folder display name (#888)

GoogleCloudPlatform · Mar 11, 2024 · cee851b · cee851b
1 parent 3bf6029
commit cee851b
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 2 deletions.
diff --git a/solutions/client-setup/README.md b/solutions/client-setup/README.md
@@ -15,8 +15,9 @@ Package to setup a client's namespaces, folder, management project and root sync
 |             Name             |              Value              | Type | Count |
 |------------------------------|---------------------------------|------|-------|
 | client-billing-id            | AAAAAA-BBBBBB-CCCCCC            | str  |     1 |
+| client-folder-display-name   | client-folder-display-name      | str  |     1 |
 | client-management-project-id | client-management-project-12345 | str  |   111 |
-| client-name                  | client1                         | str  |   149 |
+| client-name                  | client1                         | str  |   148 |
 | dns-project-id               | dns-project-12345               | str  |     1 |
 | management-namespace         | config-control                  | str  |    27 |
 | management-project-id        | management-project-12345        | str  |     6 |

diff --git a/solutions/client-setup/folder.yaml b/solutions/client-setup/folder.yaml
@@ -18,6 +18,6 @@ metadata:
   name: clients.client-name # kpt-set: clients.${client-name}
   namespace: hierarchy
 spec:
-  displayName: client-name # kpt-set: ${client-name}
+  displayName: client-folder-display-name # kpt-set: ${client-folder-display-name}
   folderRef:
     name: clients
diff --git a/solutions/client-setup/setters.yaml b/solutions/client-setup/setters.yaml
@@ -66,6 +66,9 @@ data:
   # Name for the client, lowercase only.
   # customization: required
   client-name: 'client1'
+  # Client folder display name
+  # customization: required
+  client-folder-display-name: client-folder-display-name
   #
   # Client's Billing Account ID to associate with the client's management project. The projects-sa will need billing user role permission granted.
   # alternatively, because the client management project contains very limited resources, it could be set to the core-landing-zone billing id (the projects-sa should already have permissions set during initial post deployment configurations)