If gitlab iamprofile is set in objectstorage values, a custom s3 endpoint cannot be set
In this file https://repo1.dso.mil/big-bang/bigbang/-/blob/master/chart/templates/gitlab/secret-objectstore.yaml, the s3 endpoint for each object storage configuration is wrapped into an if block with the aws manual access credentials. Recently, Gitlab enabled overriding of the STS endpoint with an environment variable which made setting the s3 endpoint independent of the STS endpoint as they now incorrectly state in their docs. Please enable setting the s3 endpoint in the storage secret here regardless of iamprofile being set or not.
Activity
added community-contribution label
added triage-kind label
added triage-priority label
@jwrate this issue has been inactive for 30 days and is being labelled as stale. If this issue is still required please take action by removing the stale label and commenting with an update, status, or justification. If this issue is not required please close it or label it as delete-me. If no action is taken this issue will be auto closed in 60 days.
added stale label
@jwrate this issue has been inactive for 60 days and is being labelled as marked-for-auto-close. If this issue is still required please take action by removing the stale and marked-for-auto-close labels and commenting with an update, status, or justification. If this issue is not required please close it or label it as delete-me. If no action is taken this issue will be auto closed in 30 days.
added marked-for-auto-close label
