tasks don't acknowledge defaults from json

[rwaffen]

when I have a bolt task with specified defaults in its json, they are ignored and I have to specify them again on the command line. Defaults should be used if specified.

[rwaffen]

task.json

{
  "description": "Disallows any new deployment and evacuates all existing container",
  "input_method": "environment",
  "parameters": {
    "force":{
      "default": false,
      "type": "Boolean"
    },
    "server":{
      "description": "The node to drain.",
      "type": "String[1]"
    }
  }
}

task.sh

#!/bin/bash

if [ "${PT_force}" == "true" ]; then
  FORCE="--force"
fi

kubectl drain $FORCE $PT_server

if i try to use the defaults i get:

mco@puppet:~$ mco tasks run adhoc::k8s_drain_node -I controller-0.example.com --server=controller-0.example.com
Retrieving task metadata for task adhoc::k8s_drain_node from the Puppet Server

Invalid input:
	 expects a value for parameter 'force'

if i specify the parameter i get this

mco@puppet:~$ mco tasks run adhoc::k8s_drain_node -I controller-0.example.com --server=controller-0.example.com --force=true

The tasks application failed to run, use -v for full error backtrace details: needless argument: --force=true

so what now.... is ist needed or not? i dont know what to do now? only to hardcode my defaults in the scripts. in bolt and pe-orchestrator this is a common pattern for a task.

[ripienaar]

As I mentioned elsewhere I think this feature was added after the choria integration for tasks was written, I do not believe we dsupport it.

We could support it, but for the medium term I would not have time to work on that.

[rwaffen]

you mentioned this in the slack. i thought maybe "somebody" could care about or has the time. if not, let's see it as a docu for others that this doesn't work, as long as it is not somewhere in the docs?