> Right. I think the use of user metadata here is wrong. It is meant for > providers like OpenStack that support key value pairs in the metadata, but > not for this. Mind changing it and add the userData field to the > DigitalOceanTemplateOptions, and also this comment to properly indicate user > metadata (in the form of arbitrary key value pairs) is not supported? Thanks!
Done. I intentionally left the old "wrong" variant via the userMetaData map in place in order to not break existing code. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/1042#issuecomment-263345268
