Support arbitrary endpoints
Bug #416109 reported by
Duncan McGreggor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Server |
Fix Released
|
High
|
Duncan McGreggor | ||
txAWS |
Fix Released
|
Medium
|
Duncan McGreggor |
Bug Description
txAWS currently has Amazon endpoints hard-coded. If it's going to support non-Amazon, EC2-compatible services, we need to make some changes. For example, developers should be able to set the port, schema, url, endpoint, etc.
Related branches
lp:~oubiwann/txaws/416109-arbitrary-endpoints
- Jamu Kakar (community): Approve
- Thomas Herve (community): Approve
- Diff: None lines
Changed in txaws: | |
assignee: | nobody → Duncan McGreggor (oubiwann) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in landscape: | |
assignee: | nobody → Duncan McGreggor (oubiwann) |
importance: | Undecided → High |
milestone: | none → 1.3.5 |
status: | New → In Progress |
summary: |
- Support flexible endpoints + Support arbitrary endpoints |
Changed in landscape: | |
status: | In Progress → Fix Committed |
tags: | added: needs-testing |
tags: | removed: needs-testing |
Changed in landscape: | |
status: | Fix Committed → Fix Released |
Changed in txaws: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'd like to be able to define a friendly name/object for services, and
then pass that in as an optional parameter when getting an api handle
-Rob