missing auth_url field in client_config template #13
Comments
Ok, right. Should be easy to fix. Working on it. |
@marcoverl Can you give a try to v0.3.0-rc1? Should work now or at least putting it into the header. wget https://github.com/Cloud-PG/dodas-go-client/releases/download/v0.3.0-rc1/dodas.zip
unzip dodas.zip
cp dodas /usr/local/bin |
it is quite strange: i obtain: but when doing the same with the dodas client i build from my forked version with the same your changes it works: The config file is: |
so the fix is ok, but no the binary? I could have done a mess with the upload :/ |
yes, please check the binary, i did my build from https://github.com/marcoverl/dodas-go-client/tree/fix-authurl |
That should be correctly updated now. Waiting for you green light before closing this and creating the PR for the next release. |
I have the same error. I've downloaded the https://github.com/Cloud-PG/dodas-go-client/archive/v0.3.0-rc1.tar.gz and did the make build on my centos7 and got the same error too. |
mmm, I can't say why, but it's not a problem to put it like that. Sorry for this many tries, but I don't have an endpoint on my side with different auth_url to test this. |
ok, it works now. |
Oh, I didn't know that. Btw, including now this into a PR vs master and closing. Feel free to reopen if anything is missing. |
Auth url now included in config parameters #13
Hello,
you should add the possibility to process the auth_url field from the config file, in order to enable deployments on those clouds where keystone server is not equal to host, e.g. like:
$ curl -v -k -H 'Content-type: text/yaml' -H 'Authorization: id = im; type = InfrastructureManager; token = '${ACCESS_TOKEN}'; \nid = ost; type = OpenStack; host = cloud-areapd.pd.infn.it; auth_version = 3.x_password; username = someuser@infn.it; password = ###; tenant = CLOUD-CERTIFICATION; domain = default; service_region = regionOne; auth_url = https://keystone-cv.pd.infn.it:443' -i -X POST https://im-dodas.cloud.cnaf.infn.it/infrastructures --data-binary "@cluster_on_cloudveneto.yaml"
The text was updated successfully, but these errors were encountered: