Slaprunner SR: resiliency: don't hardcode parameters to send.

It is done automatically through the resilient stack.

software/slaprunner/instance-resilient.cfg.jinja2

@@ -18,19 +18,6 @@ parts +=
 # Bubble up the parameters
 [request-runner]
 return = url ssh-public-key ssh-url notification-id ip backend_url url cloud9_url ssh_command password_recovery_code cloud9_backend_url
-config = instance-amount debug domain number authorized-key notify ip-list namebase runner1-computer-guid pbs-runner1-computer-guid runner2-computer-guid pbs-runner2-computer-guid runner3-computer-guid pbs-runner3-computer-guid
-# XXX Cedric LN Ugly hack, resilient stack and slaprunner stack sharing too much ssh sections
-config-authorized-key = ${request-pbs-runner-1:connection-ssh-key} ${request-pbs-runner-2:connection-ssh-key} ${slap-parameter:authorized-key}
-config-instance-amount = ${slap-parameter:instance-amount}
-config-debug = ${slap-parameter:debug}
-config-runner1-computer-guid = ${slap-parameter:runner1-computer-guid}
-config-pbs-runner1-computer-guid = ${slap-parameter:pbs-runner1-computer-guid}
-config-runner2-computer-guid = ${slap-parameter:runner2-computer-guid}
-config-pbs-runner2-computer-guid = ${slap-parameter:pbs-runner2-computer-guid}
-config-runner3-computer-guid = ${slap-parameter:runner3-computer-guid}
-config-pbs-runner3-computer-guid = ${slap-parameter:pbs-runner3-computer-guid}
-config-domain = ${slap-parameter:domain}
-
 
 [publish-connection-informations]
 recipe = slapos.cookbook:publish