Skip to content
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.

Add multiple region specification via configuration variables #46

Open
sopel opened this issue Apr 21, 2013 · 1 comment
Open

Add multiple region specification via configuration variables #46

sopel opened this issue Apr 21, 2013 · 1 comment
Assignees
Milestone

Comments

@sopel
Copy link
Owner

sopel commented Apr 21, 2013

This has been triggered by #44 and depends on #45.

Supporting the specification of multiple regions will be useful for every day operation and might also help to evaluate whether cross region support could be integrated into the AWS CLI directly instead.

  • ⚠️ Obviously care must be taken to ensure this won't break the AWS CLI in turn, a respective patch should be submitted in case.
@ghost ghost assigned sopel Apr 21, 2013
@sopel sopel modified the milestones: 1.3.0, 1.x Feb 9, 2014
@sopel
Copy link
Owner Author

sopel commented Feb 9, 2014

ℹ️ worth noting that boto has just received a most welcome refactoring to facilitate JSON-powered endpoints (see boto/boto#2045), with the explicit notion to make overriding/extending the regions/endpoints Boto has available much easier - at first sight this seems to be restricted to merge_endpoints() only right now and doesn't support region exclusion desired/required for e.g. #53 yet, but that might be easier to add now at least.

@sopel sopel modified the milestones: 1.x, 1.3.0 Feb 26, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant