Skip to content
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

Enable different internal network names #638

Open
longshuicy opened this issue Nov 27, 2024 · 0 comments · May be fixed by #639
Open

Enable different internal network names #638

longshuicy opened this issue Nov 27, 2024 · 0 comments · May be fixed by #639
Assignees

Comments

@longshuicy
Copy link
Member

Is there a generic URL so the internal client can talk to the data service, hazard service and fragility service all from the same client? The internal client works just fine with my local service because I can give it the base URL of localhost:8080, but I don't know if this same URL exists in the cluster. I'm testing the datawolf and realized if I set the internal URL for the client to "http://incore-svc-dfr3:8888/", this works just fine for talking to the dfr3 service, but when the analysis tries to talk to the hazard service, it's trying to hit http://incore-svc-dfr3:8888/hazard/api/....

Allow

@longshuicy longshuicy self-assigned this Nov 27, 2024
@longshuicy longshuicy linked a pull request Nov 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant