From 664c7f0e2814ca6d25c535290ccf8b9ba1c1ca93 Mon Sep 17 00:00:00 2001 From: Erik Sundell Date: Sat, 20 Apr 2024 12:53:38 +0200 Subject: [PATCH] Add clarity to where constraints are, basehub as compared to terraform --- terraform/aws/variables.tf | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/terraform/aws/variables.tf b/terraform/aws/variables.tf index 01e066875..f7272c32f 100644 --- a/terraform/aws/variables.tf +++ b/terraform/aws/variables.tf @@ -63,9 +63,10 @@ variable "hub_cloud_permissions" { The value is itself a map, as each hub can have multiple Kubernetes Service Accounts attached to it, for different kinds of users. The key is the name - of the Kubernetes Service Account. By convention, the currently supported keys - are are `user-sa` (for non-admin users on the hub) and `admin-sa` (for admin - users on the hub). The value can be one of: + of the Kubernetes Service Account. By convention, basehub currently only + supports creation of Kubernetes Service Accounts `user-sa` (for non-admin + users on the hub) and `admin-sa` (for admin users on the hub). The value + can be one of: 1. bucket_admin_access: List of S3 storage buckets to grant full read & write permissions to.