Closed diogokiss closed 4 years ago
I guess that this was implemented in https://github.com/terraform-providers/terraform-provider-rundeck/pull/27 and released in https://github.com/terraform-providers/terraform-provider-rundeck/releases/tag/v0.4.0. Is that correct?
This issue has been already implemented and has been released.
Hi,
In the Rundeck UI interface (since 2.6.11, at least), when you add a job reference step (let's call it job B) to an existing job (let's call it job A), it is possible to override the node filter/selection from job A, so that job B has different nodes as target.
However, the command job block doesn't seem to allow such a feature. Would it be possible to add it to the project's roadmap?
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
What should have happened?
It should be possible to define an override for the node filter in the command's job block.
Actual Behavior
What actually happened?
It is not possible to define that. In addition, if we set manually via the interface, the Terraform plan doesn't show any changes.
Steps to Reproduce
terraform apply
against the aforementioned code.rundeck_job.job-b: Refreshing state... (ID: 3fbe9d06-9ece-4373-8c47-89c56442b0a5) rundeck_job.job-a: Refreshing state... (ID: 4b0516aa-3d7a-4b2a-a2bd-3bc55aa5d143)
An execution plan has been generated and is shown below. Resource actions are indicated with the following symbols:
Terraform will perform the following actions:
rundeck_job.job-a id:
allow_concurrent_executions: "false"
command.#: "2"
command.0.description: "Does something"
command.0.shell_command: "hostname -f"
command.1.description: "Does something else using job B."
command.1.job.#: "1"
command.1.job.0.name: "job-b"
command.1.job.0.run_for_each_node: "true"
command_ordering_strategy: "node-first"
description: "This is job A."
execution_enabled: "true"
log_level: "INFO"
max_thread_count: "1"
name: "job-a"
node_filter_query: "hostname: rundeck.*"
preserve_options_order:
project_name: "testing"
rank_order: "ascending"
schedule_enabled: "true"
rundeck_job.job-b id:
allow_concurrent_executions: "false"
command.#: "1"
command.0.description: "Hello World"
command.0.shell_command: "echo 'Hello World!'"
command_ordering_strategy: "node-first"
description: "This is job B."
execution_enabled: "true"
log_level: "INFO"
max_thread_count: "1"
name: "job-b"
preserve_options_order:
project_name: "testing"
rank_order: "ascending"
schedule_enabled: "true"
Plan: 2 to add, 0 to change, 0 to destroy.
$ terraform11.14 plan -target=rundeck_job.job-a -target=rundeck_job.job-b Refreshing Terraform state in-memory prior to plan... The refreshed state will be used to calculate this plan, but will not be persisted to local or remote state storage.
rundeck_job.job-b: Refreshing state... (ID: 3fbe9d06-9ece-4373-8c47-89c56442b0a5) rundeck_job.job-a: Refreshing state... (ID: 4b0516aa-3d7a-4b2a-a2bd-3bc55aa5d143)
No changes. Infrastructure is up-to-date.