-
Notifications
You must be signed in to change notification settings - Fork 7
Add internal-server-address config option #9774
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
Conversation
|
|
||
| internal_server_address: Option[str] = Option( | ||
| "server", | ||
| "internal_server_address", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is "internal" an established term? It reads weird to me, and I would expect "local", but I don't really know anything about this domain, so this is far from a change request.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"internal" seems to be the more common term for this. "private_ip" seems to be used too, but I like that less because it can be interpreted as an IP address that belongs to a private address range.
|
I agree with your assessment on the test case. |
|
Processing this pull request |
… PR #9774) # Description Added the `server.internal-server-address` config option. Should I add a test case for this? I don't really see how to do that in a useful way. closes #9761 # Self Check: - [x] Attached issue to pull request - [x] Changelog entry - [x] Type annotations are present - [x] Code is clear and sufficiently documented - [x] No (preventable) type errors (check using make mypy or make mypy-diff) - [ ] Sufficient test cases (reproduces the bug/tests the requested feature) - [x] Correct, in line with design - [x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: ) - [ ] ~~If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see [test-fixes](https://internal.inmanta.com/development/core/tasks/build-master.html#test-fixes) for more info)~~
… PR #9774) # Description Added the `server.internal-server-address` config option. Should I add a test case for this? I don't really see how to do that in a useful way. closes #9761 # Self Check: - [x] Attached issue to pull request - [x] Changelog entry - [x] Type annotations are present - [x] Code is clear and sufficiently documented - [x] No (preventable) type errors (check using make mypy or make mypy-diff) - [ ] Sufficient test cases (reproduces the bug/tests the requested feature) - [x] Correct, in line with design - [x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: ) - [ ] ~~If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see [test-fixes](https://internal.inmanta.com/development/core/tasks/build-master.html#test-fixes) for more info)~~
|
Merged into branches master in a3eeb14 |
|
Processing #9789. |
Description
Added the
server.internal-server-addressconfig option.Should I add a test case for this? I don't really see how to do that in a useful way.
closes #9761
Self Check:
If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)