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

Ftr: registry ip:port set from enviroment variable #1036

Merged
merged 8 commits into from
Feb 23, 2021

Conversation

LaurenceLiZhixin
Copy link
Contributor

What this PR does:
Add support of "setting registry port and ip that read from environment".

  • In the past, registry ip can only be set to server local ip, whch can't set to specific ip:port by developer under the needs of specific scenarios.
  • This feature is supported in dubbo-java
    I use this feature in design of docker example
    In the docker environment example, registry ip and port should set by developer's defination, which is also dubbo-java does.
    Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


@LaurenceLiZhixin LaurenceLiZhixin changed the title Ftr/registry ip Ftr/registry ip set Feb 2, 2021
@LaurenceLiZhixin LaurenceLiZhixin changed the title Ftr/registry ip set Ftr: registry ip:port set from enviroment variable Feb 2, 2021
README_CN.md Show resolved Hide resolved
Copy link
Contributor

@Patrick0308 Patrick0308 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@AlexStocks
Copy link
Contributor

LGTM

approve instead.

@AlexStocks AlexStocks merged commit e3d1fb5 into apache:1.5 Feb 23, 2021
@cityiron cityiron added this to the v1.5.7 milestone Feb 25, 2021
AlexStocks added a commit that referenced this pull request Apr 14, 2021
Ftr: registry ip:port set from enviroment variable
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 this pull request may close these issues.

6 participants