[
https://issues.apache.org/jira/browse/JCLOUDS-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655629#comment-13655629
]
Ignasi Barrera commented on JCLOUDS-3:
--------------------------------------
As said in our conversation in the IRC, this is still not supported in the
current version of jclouds-chef. We are currently working on refactoring all
artifacts to make sure we can properly release jclouds inside the ASF, and
after that cleanup is done I'll submit the patch to add support for this issue.
Meanwhile, what you could do is create a subclass of the GroupToBootScript
class, and override the "apply" method to modify how the bootstrap script is
created to include the environment name in the "chef-client" execution line.
You can then wire your custom implementation as a Guice module when creating
the context.
> Jcloud support for custom chef environment.
> -------------------------------------------
>
> Key: JCLOUDS-3
> URL: https://issues.apache.org/jira/browse/JCLOUDS-3
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-chef
> Affects Versions: 1.7.0
> Reporter: Jayant Kaushal
> Assignee: Ignasi Barrera
>
> Jcloud support for custom chef environment.
> Trying to bootstrap a node in a different environment that _default.
> Is there a support for that
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
