https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# hobbyfarm
a
This message was deleted.
m
Same question for 
environment_specifics
variable in the 
environment
configuration. ATM, I know about the following: • region • token-secret
f
Here comes the problem: Those can by dynamic. It currently depends on the module or provisioner being used. For example a aws operator would need 
region
but another one might not. The values provided under environment_specifics will be merged with the VMT Template values + the environment override values for VMTs.
So for example our hcloud module https://github.com/svalabs/hf-tf-module-hcloud/blob/master/main.tf needs 
server_type
which specifies the sizing of the VM. This can be ifferent for every VMT.
however there are some configurations used more often or that are hardcoded into gargantua like 
ssh_username
. Eamon is currently reworking the provisioning methods - so we will change this behaviour in the next weeks anyway
m
I figured it was based per provisioner, but wasn’t seeing documentation anywhere to confirm that. Should I hold off on the provisioner docs until the updated/reworked provisioning methods are available?
f
Yes, otherwise we would have to do this twice.
m
OK, I’ll stop the work I’m currently doing and pivot to other things.
f
With the new Provisioners it will be also more easy. Provisioners will be able to register fields that are needed so this is directly documented in the UI what is needed
m
OK, that’s fantastic. Thank you.
Open in Slack
PreviousNext
Powered by