Skip to content
This repository has been archived by the owner on Mar 18, 2021. It is now read-only.

Switch consul resolver to use ServiceAddress #83

Merged
merged 2 commits into from
Sep 30, 2019

Conversation

acornies
Copy link
Collaborator

Signed-off-by: Andrew Cornies acornies@gmail.com

Signed-off-by: Andrew Cornies <acornies@gmail.com>
Signed-off-by: Andrew Cornies <acornies@gmail.com>
@orefalo
Copy link

orefalo commented Sep 19, 2019

Hi, can you maybe shed some light around this change? what's the benefit?

https://stackoverflow.com/questions/40756293/difference-between-consul-service-definition-address-and-service-address

@acornies
Copy link
Collaborator Author

Hi @orefalo This change facilitates faas-nomad on single-node instance w/ multiple interfaces (docker0 +) etc. I suspect this will be the same address as before in most use cases.

@orefalo
Copy link

orefalo commented Sep 19, 2019

Hi @acornies, that's what I understood from the link I provided, but glad you clarified. I also found you other repos; especially this one - https://github.com/acornies/faas-nomad-demos. battling vagrant (actually more vbox) on catalina at this point

@acornies acornies merged commit 5c24ad7 into master Sep 30, 2019
@acornies acornies deleted the fix/consul_service_address branch September 30, 2019 15:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants