-
Notifications
You must be signed in to change notification settings - Fork 4
issue with splitting hostname from route #26
Comments
It seems like my manifest i have provided is misleading. I have discovered that the applications:
- name: armada-core
routes:
- route: armada((domain_suffix))
<<: *defaults
path: armada-core-1.0.0-exec.jar
- name: armada-openshift
routes:
- route: armada-openshift((domain_suffix))
<<: *defaults
path: armada-openshift-1.0.0-exec.jar And this seems to be why it's defaulting to |
Hi @iKrushYou, thanks for the issue. Kind regards |
Sorry for not specifying earlier |
thx, I will check that. |
@iKrushYou |
Oh that also makes sense. I guess I kind of assumed it would work with multiple apps. Thanks for looking into it! |
I'm working on it. |
I've encountered an issue while trying various route paths (paths that used to work with the old contraband autopilot)
Here's my example:
cf zero-downtime-push armada-liquid -f pcf2/manifest.yaml --legacy-push --vars-file pcf2/vars-uat.yaml --show-crash-log
manifest.yaml
I have tried two variations so far that do not work
vars-uat.yaml
expected:
armada-openshift-uat.apps.cf2.com
result:
armada-uat.apps.cf2.com
and
vars-uat.yaml
expected:
armada-openshift.uat.apps.cf2.com
result:
error
both of these setups result in non-optimal results where the former sets all routes to
armada-uat.apps.cf2.com
instead of the full route nameand the latter just doesn't work at all
This does work with the following though:
vars-uat.yaml
To be completely honest, I don't know if it has to do with the vars file (although my guess would be no) however I am away from my work laptop right now so I wanted to post this before going to bed.
Best,
Alex
The text was updated successfully, but these errors were encountered: