-
Notifications
You must be signed in to change notification settings - Fork 21
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
support tsm servername stanzas via a defined type #7
Comments
Any progress on this? I'm in need of this very enhancement. |
Hello, we require this feature and I'm currently implementing it. The branch is heavily work in progress and not finished and tested yet but I thought it never hurts to inform early. The Branch is here: stanza_implementation_wip I try to implement it in a way that is backwards compatible, so people can update the module and migrate the data separately. Let me know what you think if you have some time to look at it. |
thank you for you work. could you open a pull request for this feature, even if it's not finished yet? i could add comments to the code in the pull request if required. toni |
Ok, opened the PR #50 |
Created a new PR with a clean commit PR #51 |
Any chance this could be integrated? We're in need of this feature aswell and we'd rather not run a custom fork. |
sorry for the delay. i'm currently busy with work, i'm going to look into this over the holidays, hopefully this is ok. thanks for your patience |
tsm::stanza { 'new_stanza':
servername => $name,
COMMethod => 'tcp',
tcpport => 35000,
tcpserveraddress => 'tsmserver.com',
config_hash => {},
}
this should be possible via a separate concat fragment.
The text was updated successfully, but these errors were encountered: