-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
all jboss_admin::resource::* types should pass their name as the name to the wrapped jboss_resource type #87
Comments
@simhpl If you want to try to do this you need to look at lib/tasks/manifest.erb, lines 64-68. That is the template used to generate all of the jboss_resources. You then need to manually update all of the resources in internal/custom_resource, because they are all over rides for the autogenerated types where needed. You then need to run the "rake resource:generate" command to generate all the new resources. Then test. Some more details on the generation can be found in the README.md in the Generating Resources section. Also see the Developer Setup section. |
@itewk |
@simhpl the jboss_resource type already has an "address" field. You should be able to update the template to pass the jboss_admin::resource::::cli_path to the jboss_resource::address field and then pass the jboss_admin::resource::::name as the jobss_resource::name to prevent the duplicate resources assuming the user passes unique names to jboss_admin::resource::* |
…as the name to the wrapped jboss_resource type
…as the name to the wrapped jboss_resource type
merged into master. |
Currently it is impossible to configure two JBoss EAP servers with the jboss_admin module because the cli_path is passed as the name to the jboss_resource type by all of the jboss_admin::resources::* types. Instead the name field of the jboss_admin::resources::* types should be passed to the wrapped jboss_resource so that conflicts can be avoided.
The text was updated successfully, but these errors were encountered: