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
Describe the bug
Push to CF fails for aws service broker.
I am trying to deploy aws service broker to CF, But i am facing this error on cf push--
ERR I0811 11:25:53.153335 28 util.go:195] Did not find 'aws_access_key' and 'aws_secret_key' in params, using default chain.
ERR I0811 11:25:53.153399 28 aws_sdk.go:71] Parameter 'target_role_name' not set. Not assuming role.
ERR I0811 11:25:57.923718 28 awsbroker.go:183] Listing objects bucket: awsservicebroker region: eu-central-1 prefix: templates/latest
ERR failed to list objects, BucketRegionError: incorrect region, the bucket is not in 'eu-central-1' region
ERR status code: 301, request id: , host id:
Although, all things are provided and aws_access_key and aws_secret_key were mentioned in manifest.yaml.
To Reproduce
After modifying the manifest.yaml when CF push command is fired, it fails.
Expected behavior
CF Push should pass
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
You need to put a "command" in manifest that looks like the one used in the packaging/cloudfoundry/tile.yml file, and make sure that all the environment variables it uses are set in your manifest too. We've literally been working on the same problem today, and it's working ;-)
Describe the bug
Push to CF fails for aws service broker.
I am trying to deploy aws service broker to CF, But i am facing this error on cf push--
Although, all things are provided and aws_access_key and aws_secret_key were mentioned in manifest.yaml.
To Reproduce
After modifying the manifest.yaml when CF push command is fired, it fails.
Expected behavior
CF Push should pass
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: