Closed jmatsushita closed 3 years ago
To clarify, this would be used in the following way by the terraform provider https://registry.terraform.io/providers/rancher/rancher2/latest/docs/resources/node_template#hetzner_config
Hi,
I've implemented the requested changes on a feature branch for now. Could you please try out the artifacts here and see if they fit your needs?
I have added the other requested items as well, except the user-data. IMO this field is more likely to contain secret information than the others, so I personally would prefer to keep it only when needed -- i.e. during the creation. I'm open for discussion, however.
Cheers
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi @JonasProgrammer, any chance the server labels will make it into the main branch? There's no reason not to and it would make creating label selector load balancers much much easier.. Thank you!
Nvm, I was using an older version. Sorry!
@stefandanaita Hi and no worries about that. I still merged the feature branch, just in case someone may find it useful in the future. Could you maybe give the this manual build a try (or build from master
yourself if you prefer)?
If everything still works as expected, I'll be happy to release a 3.6.0 tomorrow.
Worked fine for me by building from master 👀
Hey @JonasProgrammer! Any chance you can release 3.6.0? 😄
Done :)
Thank you sir! 🙏🏻
Hi there,
A couple of issues in the
terraform-rancher2-provider
would be able to move forward if the following fields where marked aspublic
so that they can be marshalled/unmarshalled:networks
https://github.com/rancher/terraform-provider-rancher2/issues/656serverLabels
https://github.com/rancher/terraform-provider-rancher2/issues/657If there aren't any reason for the other fields to be
private
I would also suggest exporting:userData
volumes
firewalls
additionalKeys
Happy to submit a PR if you agree with the intent here.
Thanks,
Jun