Git Product home page Git Product logo

concourse-pipeline-samples's Introduction

Concourse

Concourse Samples and Recipes

Sample code and recipes on Concourse CI pipelines and deployments.

Table of Contents

Concourse Pipeline Patterns

Concourse Pipeline Hacks

Concourse Deployment Patterns

Pipeline Samples

Concourse concourse_pipeline_level_secrets_path

Artifactory integration with Concourse pipelines

Blue-Green application deployment pipeline

concourse-pipeline-samples's People

Contributors

asaikali avatar bblincoe avatar bottkars avatar doddatpivotal avatar eamonryan avatar leolower avatar matthewfischer avatar matthewmcnew avatar myminseok avatar pakiheart avatar robertlk avatar thadc23 avatar tomphp avatar xetamus avatar z4ce avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

concourse-pipeline-samples's Issues

Use UAA URL for PKS cli user creation instead of hardcoded constant

Hi,

Currently, on line https://github.com/pivotalservices/concourse-pipeline-samples/blob/master/tasks/pcf/pks/configure-pks-cli-user/task.sh#L16, the hardcoded URL "api.((pcf_pks_domain))" is used for the PKS UAA url. This is instead of whatever the user has entered into the tile for that value. So the users value is ignored.

This seems like a tightly coupled dependency on using very specific URL for a given deployment. In our case, we have two PCF deployments and require PKS instances dns entries fall into same dns zone. For ex (pks-prod.a.b.c, pks-dev.a.b.c). Then we cannot use api.a.b.c for this purpose.

If this uses only uaa_url then, this would be much easier to create pks user in PKS UAA.

Thanks,
Goutam and Larry

Title: resource script '/opt/resource/check []' failed: exit status 128 ssh: Could not resolve hostname github.com: Try again

Environment:

Concourse: v1.2.3
PCF-Pipelines: Latest

Steps:

Cloned repository:

git clone https://github.com/pivotal-cf/pcf-pipelines

Modified params.yaml file:

File: params.yml

# Copyright 2017-Present Pivotal Software, Inc. All rights reserved.
#
## 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.
#
opsman_timeout_seconds: 3600 # time to wait for new OM VM to come up
#
## Either opsman_client_id/opsman_client_secret or opsman_admin_username/opsman_admin_password needs to be specified
## If you are using opsman_admin_username/opsman_admin_password, edit opsman_client_id/opsman_client_secret to be an empty value.
## If you are using opsman_client_id/opsman_client_secret, edit opsman_admin_username/opsman_admin_password to be an empty value. 
opsman_client_id: 
opsman_client_secret: 
opsman_admin_username: 
opsman_admin_password: 

opsman_ssh_password: XXXXXXXX   # ubuntu user ssh password
opsman_major_minor_version: ^2\.0\.[0-9]+$ # Ops Manager minor version to track (e.g ^2\.0\.[0-9]+$ will track 2.0.x versions)   # Ops Manager minor version to track
opsman_domain_or_ip_address: XXXXXXXXXXXXX #FQDN to access Ops Manager without protocol (will use https), ex: opsmgr.example.com
opsman_passphrase: XXXXXXXXXXXXXX
pivnet_token: XXXXXXXXXX # value must be a Pivotal Network legacy token; UAA API tokens do not work currently work
# Do not specify with a trailing slash.
vcenter_url: http://vcenter01.cglab.localnet.local
vcenter_username: [email protected]
vcenter_password: XXXXXXXXXXXXXX
vcenter_datacenter: CGLAB
vcenter_datastore: 00-SIO-PCF1_Persistent_01
vcenter_insecure: true
vcenter_ca_cert: 
# vCenter Cluster or Resource Pool to use to deploy Ops Manager.
# # Possible formats:
# #   cluster:       /<Data Center Name>/host/<Cluster Name>
# #   resource pool: /<Data Center Name>/host/<Cluster Name>/Resources/<Resource Pool Name>
vcenter_cluster: Zone01
vcenter_resource_pool: LABWORKS-CG

om_vm_folder: LABWORKS_vms
opsman_ip: 192.168.20.10
netmask: 255.255.255.0
gateway: 192.168.20.1
dns: 192.168.55.100
ntp: ntp-tx-as-1.localnet.local, ntp-ct-as-1.localnet.local
opsman_network: VLAN-XXXX
git_private_key:
opsman_disk_type: thin # use thick or thin disk provisioning

Set my concourse node:

fly -t lab login -c http://c001.cglab.localnet.local:8080

Initiated my pipeline:

$ fly -t lab set-pipeline --pipeline upgrade-opsman --config /home/concourse/pcf-pipelines/upgrade-ops-manager/vsphere/pipeline.yml --load-vars-from /home/concourse/pcf-pipelines/upgrade-ops-manager/vsphere/params.yml
resources:
  resource pcf-pipelines has been added:
+ name: pcf-pipelines
+ type: git
+ source:
+   branch: master
+   uri: [email protected]:pivotal-cf/pcf-pipelines.git
  
  resource pivnet-opsmgr has been added:
+ name: pivnet-opsmgr
+ type: pivnet
+ source:
+   api_token: CHANGEME
+   product_slug: ops-manager
+   product_version: ^2\.0\.[0-9]+$
+   sort_by: semver
  
  resource schedule has been added:
+ name: schedule
+ type: time
+ source:
+   days:
+   - Sunday
+   - Monday
+   - Tuesday
+   - Wednesday
+   - Thursday
+   - Friday
+   - Saturday
+   interval: 30m
+   location: America/Los_Angeles
+   start: 12:00 AM
+   stop: 11:59 PM
  
resource types:
  resource type pivnet has been added:
+ name: pivnet
+ type: docker-image
+ source:
+   repository: pivotalcf/pivnet-resource
+   tag: latest-final
  
jobs:
  job regulator has been added:
+ name: regulator
+ plan:
+ - get: schedule
+   trigger: true
+ - get: pivnet-opsmgr
+   params:
+     globs: []
  
  job upgrade-opsmgr has been added:
+ name: upgrade-opsmgr
+ plan:
+ - aggregate:
+   - get: pivnet-opsmgr
+     passed:
+     - regulator
+     trigger: true
+     params:
+       globs:
+       - '*.ova'
+   - get: pcf-pipelines
+ - task: wait-opsman-clear
+   file: pcf-pipelines/tasks/wait-opsman-clear/task.yml
+   params:
+     OPSMAN_CLIENT_ID: ""
+     OPSMAN_CLIENT_SECRET: ""
+     OPSMAN_DOMAIN_OR_IP_ADDRESS: XXXXXXXXXX
+     OPSMAN_PASSWORD: ""
+     OPSMAN_USERNAME: ""
+ - aggregate:
+   - task: export-opsmgr-settings
+     file: pcf-pipelines/tasks/export-opsmgr-settings/task.yml
+     params:
+       OPSMAN_CLIENT_ID: ""
+       OPSMAN_CLIENT_SECRET: ""
+       OPSMAN_DOMAIN_OR_IP_ADDRESS: XXXXXXXX
+       OPSMAN_PASSWORD: ""
+       OPSMAN_SETTINGS_FILENAME: installation.zip
+       OPSMAN_USERNAME: ""
+   - task: exported-opsmgr-diagnostic-report
+     file: pcf-pipelines/tasks/export-opsmgr-diagnostic-report/task.yml
+     params:
+       OPSMAN_CLIENT_ID: ""
+       OPSMAN_CLIENT_SECRET: ""
+       OPSMAN_DOMAIN_OR_IP_ADDRESS: XXXXXXXXX
+       OPSMAN_PASSWORD: ""
+       OPSMAN_USERNAME: ""
+ - task: deploy-opsman-vm
+   file: pcf-pipelines/tasks/deploy-opsman-vm/task.yml
+   params:
+     DNS: 192.168.55.100
+     GATEWAY: 192.168.20.1
+     GOVC_CA_CERT: ""
+     GOVC_CLUSTER: Zone01
+     GOVC_DATACENTER: CGLAB
+     GOVC_DATASTORE: 00-SIO-PCF1_Persistent_01
+     GOVC_INSECURE: "true"
+     GOVC_PASSWORD: XXXXXXXXXXXXXX
+     GOVC_RESOURCE_POOL: LABWORKS-CG
+     GOVC_URL: http://vcenter01.cglab.localnet.local
+     GOVC_USERNAME: [email protected]
+     NETMASK: 255.255.255.0
+     NTP: ntp-tx-as-1.localnet.local, ntp-ct-as-1.localnet.local
+     OPSMAN_DISK_TYPE: thin
+     OPSMAN_DOMAIN_OR_IP_ADDRESS: XXXXXXXXXXXXX
+     OPSMAN_IP: 192.168.20.10
+     OPSMAN_NETWORK: VLAN-XXXXX
+     OPSMAN_SSH_PASSWORD: XXXXXXXX
+     OPSMAN_TIMEOUT: "3600"
+     OPSMAN_VM_FOLDER: LABWORKS_vms
+ - task: import-opsmgr
+   file: pcf-pipelines/tasks/import-opsmgr-settings/task.yml
+   params:
+     OPSMAN_CLIENT_ID: ""
+     OPSMAN_CLIENT_SECRET: ""
+     OPSMAN_DOMAIN_OR_IP_ADDRESS: XXXXXXXXXXX
+     OPSMAN_PASSPHRASE: XXXXXXXXXXXXXX
+     OPSMAN_PASSWORD: ""
+     OPSMAN_SETTINGS_FILENAME: installation.zip
+     OPSMAN_USERNAME: ""
+ - task: download-stemcells
+   file: pcf-pipelines/tasks/download-pivnet-stemcells/task.yml
+   params:
+     API_TOKEN: CHANGEME
+     IAAS_TYPE: vsphere
+ - task: restore-stemcells
+   file: pcf-pipelines/tasks/restore-stemcells/task.yml
+   params:
+     OPSMAN_CLIENT_ID: ""
+     OPSMAN_CLIENT_SECRET: ""
+     OPSMAN_DOMAIN_OR_IP_ADDRESS: CHANGEME
+     OPSMAN_PASSWORD: ""
+     OPSMAN_USERNAME: ""
+ - task: apply-changes
+   file: pcf-pipelines/tasks/apply-changes/task.yml
+   params:
+     OPSMAN_CLIENT_ID: ""
+     OPSMAN_CLIENT_SECRET: ""
+     OPSMAN_DOMAIN_OR_IP_ADDRESS: XXXXXXXXXX
+     OPSMAN_PASSWORD: ""
+     OPSMAN_USERNAME: ""
  
apply configuration? [yN]: y
pipeline created!
you can view your pipeline here: http://jump001.cglab.localnet.local:8080/teams/main/pipelines/upgrade-opsman

local: ~> fly -t lab unpause-pipeline -p upgrade-opsman
unpaused 'upgrade-opsman'
local: ~> 

Error posted:

stderr:
Cloning into '/tmp/git-resource-repo-cache'...
ssh: Could not resolve hostname github.com: Try again
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Looked at log files under concourse (systemD concourse-web and concourse-woker), but do not see anything that catches the eye...

Is there any log verbosity level I can increase or if anyone point me to a right direction?

Thanks so much

Thank You, {{PARAMS}} Doesn't seem to work

Awesome work, .... you illustrate

type: docker-image
source:
repository: 192.168.99.100:5000/ubuntu
tag: "latest"
insecure_registries: [ "192.168.99.100:5000" ]

Trying to do something like this

type: docker-image
source:
repository: {{GRADLE_RESOURCE}}
tag: "latest"
insecure_registries: [ {{DOCKER_REGRISTRY}} ]

I set the pipeline with --var GRADLE_RESOURCE=192.168.1.122:5000/gradle

Get the following error:
failed to load source-code/ci/tasks/unit.yml: yaml: invalid map key: map[interface {}]interface {}{"GRADLE_RESOURCE":interface {}(nil)}

Any Thoughts on why the Params dont work? or a work around

PKS 1.1.0 GA parameters not included for master & worker service account

Hi,
The parameters in Kubernetes Cloud Provider page shown below are not listed in the pks_params.yml. And these take email values instead of json keys. Ref

.properties.cloud_provider.gcp.master_service_account
.properties.cloud_provider.gcp.worker_service_account

Please add these attributes in the params file.

Thanks,
Goutam Tadi

getting :-errors while sending mail with attachments

error details ๐Ÿ‘Ž
: Error: connect EINVAL 0.0.4.210:465 - Local (0.0.0.0:0)
at Object.exports._errnoException (util.js:1036:11)
at exports._exceptionWithHostPort (util.js:1059:20)
at connect (net.js:874:16)
at net.js:1003:7
at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:62:16)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:81:10)
code: 'ECONNECTION',
errno: 'EINVAL',
syscall: 'connect',
address: '0.0.4.210',
port: 465,
command: 'CONN' }

yaml file:-

resources:

jobs:

  • name: send-email-with-attachment
    serial: true
    public: true
    plan:
    • do:

      • get: pipeline-scripts
        trigger: false

      • task: prep-email-text
        config:
        platform: linux
        image_resource:
        type: docker-image
        source:
        repository: pivotalservices/concourse-send-email
        tag: "latest"
        outputs:
        - name: email-text
        run:
        path: sh
        args:
        - -exc
        - |
        echo "Hello Concourse user" > ./email-text/email-subject.txt
        echo "This email is from my Concourse pipeline. You will find my file attached. Thanks!" > ./email-text/email-body.txt

      • task: send-email-with-attachment
        file: pipeline-scripts/email-with-attachments/ci/tasks/send-email.yml
        params:
        SMTP_HOST: {{smtp-host}}
        SMTP_PORT: {{smtp-port}}
        SMTP_USERNAME: {{smtp-username}}
        SMTP_PASSWORD: {{smtp-password}}
        EMAIL_FROM: {{email-from}}
        EMAIL_TO: {{email-to}}
        EMAIL_SUBJECT_FILE: ./email-text/email-subject.txt
        EMAIL_BODY_FILE: ./email-text/email-body.txt
        EMAIL_ATTACHMENTS: '[{ "filename": "my-attachment.txt","path": "./pipeline-scripts/email-with-attachments/my-attachment.txt", "contentType":"text/plain"}]'

      on_failure:
      task: email-notification-failure
      file: pipeline-scripts/email-with-attachments/ci/tasks/send-email.yml
      params:
      SMTP_HOST: {{smtp-host}}
      SMTP_PORT: {{smtp-port}}
      SMTP_USERNAME: {{smtp-username}}
      SMTP_PASSWORD: {{smtp-password}}
      EMAIL_FROM: {{email-from}}
      EMAIL_TO: {{email-to}}
      EMAIL_SUBJECT_TEXT: Pipeline failure
      EMAIL_BODY_TEXT: This is the report of a pipeline failure. See attachment for more info.
      EMAIL_ATTACHMENTS: '[{ "filename": "my-attachment.txt","path": "./pipeline-scripts/email-with-attachments/my-attachment.txt", "contentType":"text/plain"}]'

it is failing when it si going to call the node pipeline-scripts/email-with-attachments/ci/scripts/send-email.js

Concourse pipelines with a local Docker Registry example is throwing error: invalid configuration error

The local docker registry tutorial [https://github.com/pivotalservices/concourse-pipeline-samples/tree/master/private-docker-registry] is already 2 years old, so maybe it's just outdated, but when I try to apply the inline-pipeline.yml I am getting an invalid configuration error

Output is below

`$ fly -t lite set-pipeline -p test-registry -c inline-pipeline.yml
groups:
group main has been added:
name: main
jobs:
- check-os-version
- issue-ls-command

resources:
resource concourse-pipeline-samples has been added:
name: concourse-pipeline-samples
type: git
source:
branch: master
uri: https://github.com/pivotalservices/concourse-pipeline-samples.git

jobs:
job check-os-version has been added:
name: check-os-version
public: true
serial: true
plan:
- get: concourse-pipeline-samples
trigger: true
- task: check-image-os-version
config:
platform: linux
image_resource:
type: docker-image
source:
insecure_registries:
- 172.20.10.2:5000
repository: 172.20.10.2:5000/ubuntu
tag: latest
run:
path: cat
inputs:
- name: concourse-pipeline-samples
path: ""
optional: false

job issue-ls-command has been added:
name: issue-ls-command
public: true
serial: true
plan:
- get: concourse-pipeline-samples
passed:
- check-os-version
trigger: true
- task: issue-ls-command
config:
platform: linux
image_resource:
type: docker-image
source:
insecure_registries:
- 172.20.10.2:5000
repository: 172.20.10.2:5000/ubuntu
tag: latest
run:
path: ls
inputs:
- name: concourse-pipeline-samples
path: ""
optional: false

apply configuration? [yN]: y
error: invalid configuration:
unknown/extra keys:

  • jobs[0].plan[1].config.args
  • jobs[1].plan[1].config.args`

Backing up ERT is throwing this error "there was an error getting tile from registry: invalid cli flag args" and not working

my PCF is SAML integrated. opsman backup works with this pipeline. ERT backup failes with this error "there was an error getting tile from registry: invalid cli flag args"

root@84a414a4-9a02-4e72-5fc9-87ed844b7523:/tmp/build/dd733a1a# sh -x ./cfops_backup.sh

  • set -e
  • export LOG_LEVEL=debug
  • export no_proxy=.dfs.com
  • ops_manager_ui_user=admin
  • target_tile=elastic-runtime
  • ops_manager_ui_password=xxxxx
  • export CFOPS_ADMIN_USER=admin
  • export CFOPS_ADMIN_PASS=xxxxx
  • export CFOPS_OM_USER=ubuntu
  • export CFOPS_OM_PASS=xxxxx
  • export CFOPS_CLIENT_ID=admin
  • export CFOPS_CLIENT_SECRET=xxxxxx
  • echo TARGET TILE: elastic-runtime
    TARGET TILE: elastic-runtime
  • echo OPS_MANAGER_HOSTNAME: pcfdev.dfs.com
    OPS_MANAGER_HOSTNAME: pcfdev.dfs.com
  • echo FILE_REPO_IP: 1.1.0.15
    FILE_REPO_IP: 1.1.0.15
  • echo FILE_REPO_SPACE:
    FILE_REPO_SPACE:
  • echo FILE_REPO_PATH: /opt/app/pcf_backups
    FILE_REPO_PATH: /opt/app/pcf_backups
  • date +%Y%m%d
  • export datestring=20170922
  • export build_dir=/tmp/build/dd733a1a
  • echo Current directory: /tmp/build/dd733a1a
    Current directory: /tmp/build/dd733a1a
  • export backup_root_dir=/tmp/build/dd733a1a/backupdir
  • export backup_parent_dir=/tmp/build/dd733a1a/backupdir/20170922
  • export backup_file_destination=/tmp/build/dd733a1a/backupdir/20170922/elastic-runtime
  • mkdir -p /tmp/build/dd733a1a/backupdir/20170922
  • mkdir -p /tmp/build/dd733a1a/backupdir/20170922/elastic-runtime
  • chmod a+x ./cfops_linux64/cfops_linux64
  • ./cfops_linux64/cfops_linux64 list-tiles
    2017/09/22 23:01:58 D0922 23:01:58.592521 346 init.go:38] not loading plugins: open ./plugins: no such file or directory []
    Available Tiles:
    ops-manager
    elastic-runtime
  • echo Executing cfops command...
    Executing cfops command...
  • ./cfops_linux64/cfops_linux64 backup --opsmanagerhost pcfdev.dfs.com -d /tmp/build/dd733a1a/backupdir/20170922/elastic-runtime --tile elastic-runtime
    2017/09/22 23:01:58 D0922 23:01:58.601938 351 init.go:38] not loading plugins: open ./plugins: no such file or directory []
    2017/09/22 23:01:58 D0922 23:01:58.602346 351 createCliCommand.go:85] checking registry for 'elastic-runtime' tile
    2017/09/22 23:01:58 D0922 23:01:58.60245 351 createCliCommand.go:88] found tile in registry
    2017/09/22 23:01:58 D0922 23:01:58.602623 351 createCliCommand.go:338] OpsManagerHost: pcfdev.dfs.com
    2017/09/22 23:01:58 D0922 23:01:58.602689 351 createCliCommand.go:339] AdminUser: admin
    2017/09/22 23:01:58 D0922 23:01:58.602849 351 createCliCommand.go:340] AdminPass: xxxxxx
    2017/09/22 23:01:58 D0922 23:01:58.602999 351 createCliCommand.go:341] OpsManagerUser: ubuntu
    2017/09/22 23:01:58 D0922 23:01:58.603062 351 createCliCommand.go:342] OpsManagerPass: xxxxxx
    2017/09/22 23:01:58 D0922 23:01:58.603224 351 createCliCommand.go:343] Destination: /tmp/build/dd733a1a/backupdir/20170922/elastic-runtime
    2017/09/22 23:01:58 E0922 23:01:58.603449 351 createCliCommand.go:57] there was an error getting tile from registry: invalid cli flag args
    NAME:
    cfops_linux64 backup - creates a backup archive of the target tile

USAGE:
cfops_linux64 backup [command options] [arguments...]

DESCRIPTION:
backup --opsmanagerhost --adminuser --adminpass --opsmanageruser --opsmanagerpass --omr -d

--tile elastic-runtime

OPTIONS:
--pluginargs value, -p value Arguments for plugin to execute [$CFOPS_PLUGIN_ARGS]
--adminpass value, --dp value password for Ops Mgr admin (Ops Manager WebConsole Credentials) [$CFOPS_ADMIN_PASS]
--opsmanageruser value, --omu value username for Ops Manager VM Access (used for ssh connections) [$CFOPS_OM_USER]
--opsmanagerpass value, --omp value password for Ops Manager VM Access (used for ssh connections) [$CFOPS_OM_PASS]
--clientid value, --cid value client ID if using a UAA client instead of a UAA user [$CFOPS_CLIENT_ID]
--tile value, -t value a tile you would like to run the operation on [$CFOPS_TILE]
--nfs value options are 'lite' (skips optional parts of blobstore), 'full' (backs up whole blobstore) or 'bp' (only backs up buildpacks). This will only apply to elastic-runtime. Defaults to 'full' (default: "full") [$NFS_BACKUP]
--admintoken value, --dt value Ops Mgr OAuth admin token (not required if adminuser and adminpass are provided) [$CFOPS_ADMIN_TOKEN]
--adminuser value, --du value username for Ops Mgr admin (Ops Manager WebConsole Credentials) [$CFOPS_ADMIN_USER]
--clientsecret value, --cis value client secret if using a UAA client instead of a UAA user [$CFOPS_CLIENT_SECRET]
--opsmanagerhost value, --omh value hostname for Ops Manager [$CFOPS_HOST]
--opsmanagerpassphrase value, --omr value passphrase is used by Ops Manager 1.7 and above to decrypt the installation files during restore [$CFOPS_OM_PASSPHRASE]
--encryptionkey value, -k value encryption key to encrypt/decrypt your archive (key lengths supported are 16, 24, 32 for AES-128, AES-192, or AES-256) [$CFOPS_ENCRYPTION_KEY]
--clear-bosh-manifest value set this flag if you would like to clear the bosh-deployments.yml (this should only affect a restore of Ops-Manager) [$CFOPS_CLEAR_BOSH_MANIFEST]
--destination value, -d value path of the Cloud Foundry archive [$CFOPS_DEST_PATH]

root@84a414a4-9a02-4e72-5fc9-87ed844b7523:/tmp/build/dd733a1a#

Install PKS pipeline fails to stage PKS-1.1.0-rc1 (early access) release on Ops Manager

Hi,

We used this pipeline previously to install all GA releases of PKS and was working fine.
We got access to PKS-1.1.0-rc1 early release and tried to install with the same pipeline.yml with updated params.

Upload product to Ops Manager was successful. However when staging the product, we are facing the issue explained below:

X-Xss-Protection: 1; mode=block
Archive:  ./pivnet-product/pivotal-container-service-1.1.0-build.283.pivotal
  inflating: metadata/metadata.yml   
	Need exactly one unstaged build for pivotal-container-service version 1.1.0-rc1
[]

Is there a way to support this early access stage and install ?
What can we do as a temporary/permanent measure to solve this?

Thanks,
Goutam Tadi
Greenplum-for-Kubernetes

Deleting PKS cluster should be non-interactive

When running the delete-pks-cluster task, deletion times out because the --non-interactive flag is not passed here:

https://github.com/pivotalservices/concourse-pipeline-samples/blob/a5c64bc017cfb58949932bb20fa1c3949f30ae4d/tasks/pcf/pks/delete-pks-cluster/task.sh#L8

Example output:

Deleting PKS cluster [cluster-name]...

Are you sure you want to delete cluster cluster-name? (y/n): Error: Unable to read confirmation input: timeout waiting for user input
you may want to use --non-interactive

Docker images are 2 years out of date

The docker images used in many of the pipelines have not been updated in two years. If you are not automatically updating the images, I'd suggest using someone else's images as many users will copy/paste the examples provided.

install-pks pipeline has hardcoded vsphere

the upload-tile task has vsphere hardcoded as the IAAS:

task: upload-tile
    file: pcf-pipelines/tasks/upload-product-and-stemcell/task.yml
    params:
      IAAS: vsphere

It would be good if it would switch to "google" when you set GCP as the target.

task: upload-tile
    file: pcf-pipelines/tasks/upload-product-and-stemcell/task.yml
    params:
      IAAS: google

send-email is not sending the email.

Can you please update on why the below would not send an email?

put: send-email
params:
to: [[email protected]]
subject: ./email-text/email-subject.txt
body: ./email-text/email-body.txt

send-email (from the output)

Using dir /tmp/build/get
Logging payload to /tmp/tmp4t1hp1un

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.