Adds no_proxy input to create_overcloudrc workflow
When the create_overcloudrc workflow was first introduced, it did not provide an input argument for the no_proxy argument of the primary action it calls. This patch adds the no_proxy input argument to the create_overcloudrc workflow, ensures the argument is passed to the underlying action and updates the description of the workflow to notify users of the optional no_proxy list. Change-Id: I6074b4085b5b77f010f5f2972e7b120aa344f6c5 fixes-bug: 1776930
This commit is contained in:
parent
33e8979c7f
commit
258748674a
|
@ -499,7 +499,8 @@ workflows:
|
|||
|
||||
create_overcloudrc:
|
||||
description: >
|
||||
Given the name of a container, generate the overcloudrc files
|
||||
Given the name of a container and optionally a comma-separated string
|
||||
of hosts that shouldn't be proxied, generate the overcloudrc files
|
||||
needed to access the overcloud via the CLI.
|
||||
|
||||
tags:
|
||||
|
@ -507,6 +508,7 @@ workflows:
|
|||
|
||||
input:
|
||||
- container: overcloud
|
||||
- no_proxy: ''
|
||||
- queue_name: tripleo
|
||||
|
||||
tasks:
|
||||
|
@ -514,6 +516,7 @@ workflows:
|
|||
action: tripleo.deployment.overcloudrc
|
||||
input:
|
||||
container: <% $.container %>
|
||||
no_proxy: <% $.no_proxy %>
|
||||
on-complete: send_message
|
||||
publish-on-error:
|
||||
status: FAILED
|
||||
|
|
Loading…
Reference in New Issue