-
Notifications
You must be signed in to change notification settings - Fork 657
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"bosh micro deploy" proxy support #77
Comments
Can you try setting
That should take care of the communication with the AWS API endpoint, but there are later steps which I still think will fail... |
Hi, I had a try by adding ---
name: aws
logging:
level: DEBUG
network:
type: dynamic
vip: xx.xx.xx.xx
resources:
persistent_disk: 20000
cloud_properties:
instance_type: m1.small
availability_zone: eu-west-1a
cloud:
plugin: aws
properties:
aws:
access_key_id: xxxxxxxxxxxxxxxxxxx
secret_access_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
proxy_uri: http://10.144.1.10:8080
default_key_name: bosh
default_security_groups: ["bosh"]
ec2_private_key: ~/.ssh/bosh.pem
ec2_endpoint: ec2.eu-west-1.amazonaws.com
apply_spec:
agent:
blobstore:
address: xx.xx.xx.xx
nats:
address: xx.xx.xx.xx
properties:
aws_registry:
address: xx.xx.xx.xx |
Martin, was his config correct? |
It looks like it is correct |
@tsaleh - Can you comment? |
Hi @qch1843 - proxy support is something we'd be happy to accept if given a pull request, but not something that's currently prioritized on the roadmap. I'm going to close this issue. Please reference it if you (or anyone else) want to take it on as a PR. |
Hi,
I seems "bosh micro deploy" doesn't work from behind a proxy? (https://groups.google.com/a/cloudfoundry.org/forum/#!topic/bosh-users/kJ6PCC1CN5A)
Could the proxy support be added? Most of the corporate users are behind firewall/proxy.
Thanks,
Steven
The text was updated successfully, but these errors were encountered: