833-gitlab-object-storage-use_iam_role

Summary

With the current way the Big Bang chart is set up, the users are unable to use an iam profile for their aws object storage in the gitlab chart. The chart will include the accesskey and secretkey with empty values and no use_iam_profile key.

Resolution

Following these docs

Added a new key and logic into the gitlab template to handle use of an iam profile for gitlab.

Closes #833 (closed)

chart/values.yaml

@@ -655,7 +655,7 @@ addons:
       region: ""
 
       # -- Access key for connecting to object storage endpoint.
-      # -- If using accessKey and accessSecret, the iamProfile must be left as empty string: ""
+      # -- If using accessKey and accessSecret, the iamProfile must be left as an empty string: ""
       accessKey: ""
 
       # -- Secret key for connecting to object storage endpoint.
@@ -666,8 +666,8 @@ addons:
       # Example: "prod" will produce "prod-gitlab-bucket"
       bucketPrefix: ""
 
-      # -- Name of iam profile to use.
-      # -- If using an iam profile, the accessKey and accessSecret must be left as empty string: ""
+      # -- Name of AWS IAM profile to use.
+      # -- If using an AWS IAM profile, the accessKey and accessSecret values must be left as empty strings eg: ""
       iamProfile: ""
 
     # -- Values to passthrough to the gitlab chart: https://repo1.dso.mil/platform-one/big-bang/apps/developer-tools/gitlab.git