slaprunner: resilient instance publishs monitor parameters

Conflicts:
	software/slaprunner/instance-resilient.cfg.jinja2
	software/slaprunner/instance-runner.cfg

software/slaprunner/instance-resilient.cfg.jinja2

@@ -17,15 +17,19 @@ parts +=
 
 # Bubble up the parameters
 [request-runner]
-return = url ssh-public-key ssh-url notification-id ip backend_url url ssh_command password_recovery_code shell_password access_url 1_info
+return = url ssh-public-key ssh-url notification-id ip backend_url url ssh_command password_recovery_code shell_password access_url 1_info 2_info control_url monitor_url IMPORTANT_monitor_info
 
 [publish-connection-informations]
 recipe = slapos.cookbook:publish
 1_info = ${request-runner:connection-1_info}
+2_info = ${request-runner:connection-2_info}
 backend_url = ${request-runner:connection-backend_url}
 access_url = ${request-runner:connection-access_url}
 url = ${request-runner:connection-url}
 ssh_command = ${request-runner:connection-ssh_command}
+control_url = ${request-runner:connection-control_url}
+monitor_url = ${request-runner:connection-monitor_url}
+IMPORTANT_monitor_info = ${request-runner:connection-IMPORTANT_monitor_info}
 
 [slap-parameter]
 # Default parameters for distributed deployment

software/slaprunner/instance-runner.cfg

@@ -359,6 +359,7 @@ return = site_url domain
 [publish-connection-informations]
 recipe = slapos.cookbook:publish
 1_info = On your first run, Use "access_url" to setup you account.Then you can use both "url" or "access_url". Or "backend_url" if you want to use ipv6.
+2_info = In order to set up your account, get the recovery-code from the control interface (see control_url). Before read the notification on monitor_info
 backend_url = $${slaprunner:access-url}
 access_url = $${:url}/login
 url =  https://$${request-frontend:connection-domain}