This repository has been archived by the owner on Oct 21, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Add DigitalOcean provisioner #318
Comments
Not out-of-scope, feel free |
@odacremolbap are @StackPointCloud planing upstreaming the digitalocean-provisioner? |
can't wait for this! |
Feel free to checkout #470 |
OMG!!!
2017-11-23 14:10 GMT+01:00 Kristian Klausen <[email protected]>:
… can't wait for this!
Feel free to checkout #470
<#470>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#318 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABouenTIrxx0Wprmub9XarU--zOnd9Bgks5s5W7BgaJpZM4PD7Ox>
.
--
Cheers,
// Tim Brandin @timbrandin <https://twitter.com/#!/timbrandin>
http://timbrandin.com
http://studiointeract.com
|
Please report back if you try it out :) |
Closed by: #470 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello
Would it be out-of-scope for this repo, to include a DigitalOcean provisioner/flexvolume? or is it too provider specific?
I'm just asking before starting working on a PR.
The text was updated successfully, but these errors were encountered: