Cannot use image "slugs" when creating servers

[taylorotwell]

I've been trying this for several days off and on and can't get this to work. Passing ubuntu-14-04-x64 in the "image id" field will not work. I get invalid image errors. Using the BuzzAdapter.

[yassirh]

What version are you using?

[taylorotwell]

Latest stable tag.

On October 21, 2014 at 3:51:37 PM, Hannoun Yassir (notifications@github.com) wrote:

What version are you using?

—
Reply to this email directly or view it on GitHub.

[yassirh]

Can you try the newest release?

[taylorotwell]

Now I have even bigger problems. Neither works:

http://d.pr/i/10vvR/30KsrWnl

[taylorotwell]

I had to fork this library and hack in some changes because it is way too brittle against API changes in the way it is throwing exceptions even if DigitalOcean simply adds a new property. Had broken Laravel Forge entirely.

[yassirh]

@taylorotwell Are you using the Laravel wrapper?

[GrahamCampbell]

That doesn't make much difference. All my wrapper does is instantiate the classes, nothing more.

[taylorotwell]

No I'm not. Plain library.

On Saturday, October 25, 2014, Graham Campbell notifications@github.com
wrote:

That doesn't make much difference. All my wrapper does is instantiate the
classes, nothing more.

—
Reply to this email directly or view it on GitHub
#43 (comment)
.

[yassirh]

@GrahamCampbell can you reproduce this error?

here is the code i'm using to test :

$adapter = new GuzzleAdapter('MY TOKEN');
$digitalOcean = new DigitalOceanV2($adapter);

$droplet = $digitalOcean->droplet();
try {
    echo "<pre>";
    var_dump($droplet->create("test", "nyc1", "512mb", "ubuntu-14-04-x64"));
    echo "</pre>";
} catch (Exception $e) {
    die($e->getMessage());
}

[GrahamCampbell]

I don't have any time right now, but I can have a go tomorrow or the day after. Ping me in 48 hours if I forget.

[yassirh]

@taylorotwell are you still getting this error with the latest version 0.2 or the master branch?

[taylorotwell]

It’s fixed.

On Mon, Oct 27, 2014 at 2:34 PM, Hannoun Yassir notifications@github.com
wrote:

@taylorotwell are you still getting this error with the latest version 0.2 or the master branch?

Reply to this email directly or view it on GitHub:
#43 (comment)