airshipctl/playbooks/vars/local-dev.yaml
Yasin, Siraj (SY495P) 458fb2579b Fix gate scripts for local setup
* when remote_work_dir is set, document pull happens from the
  remote_work_dir (/tmp/airship) with a folder created within
  remote_work_dir with repo name (/tmp/airship/airshipctl).
  However the manifest yamls of kind "Clusterctl"
  refers to a relative path from work_dir and it fails
  finding expected objects.
   example: manifests/function/capm3/v0.3.1
* So trying to avoid document pull, and use current dir for workspace.
  similar to Zuul gate implementation

Change-Id: I63fd5476247f957745e15cbdfceb5fb483758e83
2020-06-12 03:00:32 +00:00

24 lines
1.1 KiB
YAML

# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
proxy:
enabled: "{{ lookup('env', 'USE_PROXY', default='false') }}"
http: "{{ lookup('env', 'HTTP_PROXY', default='') }}"
https: "{{ lookup('env', 'HTTPS_PROXY', default='') }}"
noproxy: "{{ lookup('env', 'NO_PROXY', default='') }}"
# If remote_work_dir is defined, the deployment script will invoke airshipctl
# document pull command to download the manifests to the remote_work_dir.
# Otherwise, the current working dir where the script is launched is used and
# document pull is skipped.
#remote_work_dir: "/tmp/airship"