-
Notifications
You must be signed in to change notification settings - Fork 104
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
Add fixes for optional uaa-target flag #640
Conversation
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story. The labels on this github issue will be updated when the story is started. |
Hi @sneal - sorry it took so long for someone to review this. I pulled in the changes today and rebased main onto the branch, then ran tests by running the following:
Unfortunately there were quite a few test failures resulting from your changes:
These two results can be ignored:
I'm happy to chat further about this if you'd like to. Sorry again for the delay in response! |
@rhall-pivotal Would you like me to rebase the branch? I don't get the unauthenticated_client.go compilation errors on the |
@sneal - yes if you could. I'll re-pull and re-test again once you have rebased. |
- The UAA target defaults to /uaa on Operations Manager, but can now be overridden in cases where UAA is not located at the default location. - Consistently parse target and allow http(s):// protocol prefix.
@sneal - Testing locally produced better results this time. merging |
Lazily validate target URLs to avoid interfering with connectionless commands like help and interpolate