Custom ports for EC2 compatible APIs #24
Open
Conversation
This file contains 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
|
To get rid of any potential confusion of why you might need this: We're running an OpenStack based Private-Cloud which emulates the EC2 API and additionally offers it's own OpenStack API on 2 different ports therefore I needed the option to choose the port individually. |
|
@mirkok is it possible to get this committed? I have a similar need where I'd like to create an ec2 client using host/port to a mock ec2 api server in order to write tests around various ec2 api responses. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added the option for adding a custom port when needed otherwise it will drop back to the default port based on the 'secure' attribute. Think it's way easier than redirecting the port server side.