On 3 May 2014 05:27, Chris Fordham <[email protected]> wrote:
> How about an API to retreive current/lastest AMI IDs by release, region > etc.? > > > On Fri, May 2, 2014 at 11:53 PM, Marcin Kulisz <[email protected]> wrote: > >> On 2014-05-01 13:04:46, Brian Gupta wrote: >> > On Thu, May 1, 2014 at 11:49 AM, James Bromberger <[email protected]> >> wrote: >> >> snip >> >> > I'll add that although it doesn't cost much to host AMIs, forcing our >> > users who are using unmodified AMIs to clone ours, to rely on them >> > being there, doesn't seem ideal. >> >> But it's a good practise to not to rely on external repos including AMIs. >> I'm not sure how fast we should remove AMIs but having AMI cloned into >> your own >> account when using it in production seams to be a way to go in my opinion. >> -- >> >> |_|0|_| | >> |_|_|0| "Heghlu'Meh QaQ jajVam" | >> |0|0|0| -------- kuLa --------- | >> >> gpg --keyserver pgp.mit.edu --recv-keys 0x58C338B3 >> 3DF1 A4DF C732 4688 38BC F121 6869 30DD 58C3 38B3 >> > > > How about an API to retreive current/lastest AMI IDs by release, region etc.? Eric Hammond actually suggested implementing his API, when we discussed that topic the last time. Have a look at the archive: https://lists.debian.org/debian-cloud/2012/11/msg00142.html
