Extend objectscript.conn.docker-compose settings object to handle superserver port identification
#1485
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
isc-bsaviano
approved these changes
Feb 21, 2025
Contributor
isc-bsaviano
left a comment
isc-bsaviano
left a comment
There was a problem hiding this comment.
Looks good but I don't use this feature so have not tested
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR closes #1243
It will make the recently added
asyncServerForUriAPI function resolve a Docker container connection's local superserver port intoserver.superserverPort, allowing future development in other extensions such as Server Manager to identify the superserver port of container-type connections as well as for ordinary ones.