Bug #37305: Remote execution ignores default values for template inputs when triggering jobs through the api - Foreman Remote Execution - Foreman

Actions

Copy link

Bug #37305

closed

Remote execution ignores default values for template inputs when triggering jobs through the api

Added by Adam Ruzicka about 2 months ago. Updated 6 days ago.

Status:

Closed

Priority:

Normal

Assignee:

Adam Ruzicka

Category:

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman_remote_execution/pull/880

Fixed in Releases:

foreman_remote_execution-13.1.0

Found in Releases:

Red Hat JIRA:

Description

Steps to reproduce:
1) Import the attached job template
2) Try to run it with curl without providing a value for the foo input

curl -u admin:changeme http://foreman-r3.orb.local:5000/api/v2/job_invocations -X POST -d '{"job_invocation": {"job_template_id": 187, "search_query": "name ~ *", "targeting_type": "static_query", "inputs": {}}}' -H 'Content-Type: application/json'

Note, the template had id 187 on my box

<%#
name: Foo
snippet: false
template_inputs:
- name: foo
  required: false
  input_type: user
  advanced: false
  value_type: plain
  default: '1'
  hidden_value: false
model: JobTemplate
job_category: Miscellaneous
provider_type: script
kind: job_template
organizations:
- Default Organization
locations:
- Default Location
%>

<%= input['foo'] %>