Yeah, it's a little odd.  The problem is that Vagrant doesn't have any
global rackspace config - it's per machine.  You could use different
regions - or even different credentials - on each machine.

So... I'm getting the connection based on the machine, and then using that
connection to query (the account/region) for flavors/images.


On Thu, Feb 27, 2014 at 4:14 PM, Kyle Rames <notifications@github.com>wrote:

> In README.md:
>
> > @@ -79,6 +79,23 @@ Note that normally a lot of this boilerplate is encoded within the box
> >  file, but the box file used for the quick start, the "dummy" box, has
> >  no preconfigured defaults.
> >
> > +## Custom Commands
> > +
> > +The plugin includes two custom vagrant commands.  One gives you a list of available
> > +images you can use and the other gives a list of available flavors.
> > +
> > +```
> > +vagrant rackspace images
> > +vagrant rackspace flavors
> > +```
> > +
> > +If your Vagrantfile contains multiple machines, then you can pass the machine name
> > +to the command to get the possible images/flavors for that machine only:
> > +```
> > +vagrant rackspace images <name>
>
> This isn't immediately clear to me. Are you querying a vm for its
> flavor/image? Or are querying a region?
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/mitchellh/vagrant-rackspace/pull/75/files#r10142592>
> .
>