You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running AWS Service Broker on OpenShift 3.7 and tried, according to these instructions, to hide some sensitive parameters from Service Catalog users (aws_access_key, aws_secret_key, etc).
I've correctly created the secret within the same namespace where the broker is running (aws-service-broker in my case) and updated the broker-config configmap. After restart, the broker bootstraped correctly but when it gets requests from the Service Catalog it didn't hide the parameters from the Service Provisiong Wizard. I can see the following message in the broker logs:
[2019-03-06T16:24:32.778Z] [WARNING] - Unable to load secret 'aws-access-secret' from namespace ''
Problem
I'm running AWS Service Broker on OpenShift
3.7
and tried, according to these instructions, to hide some sensitive parameters fromService Catalog
users (aws_access_key, aws_secret_key, etc).I've correctly created the secret within the same namespace where the broker is running (
aws-service-broker
in my case) and updated thebroker-config
configmap. After restart, the broker bootstraped correctly but when it gets requests from the Service Catalog it didn't hide the parameters from the Service Provisiong Wizard. I can see the following message in the broker logs:Solution
Please add the following notes to this documentation section:
Make sure to set the
namespace
parameter to the ASB project's name so the broker can fetch the secrets.If the
namespace
parameter is omitted the broker won't read the secrets.The text was updated successfully, but these errors were encountered: