pivotal / docs-platform-automation Goto Github PK
View Code? Open in Web Editor NEWdocs repo for the Platform Automation package
Home Page: https://docs.pivotal.io/platform-automation/
License: Other
docs repo for the Platform Automation package
Home Page: https://docs.pivotal.io/platform-automation/
License: Other
URL or GitHub link to the page where you're having the issue
https://docs.pivotal.io/platform-automation/v4.3/tasks.html#upgrade-opsman
Is your request for a change or addition to content related to a problem? If so, please describe.
It wasn't clear how to utilize $timestamp
for non-versioned s3 state.yml files, but we were able to find the solution looking at the comments in delete-vm
Describe the solution you'd like
Add similar text from delete-vm to upgrade-opsman i.e
# - Required
# - Filepath of the state yaml file
# - The path is relative to root of the `state` output
# - if the filename includes "$timestamp",
# for example "state-$timestamp.yml",
# the final filename will include the current timestamp.
# - this is necessary if using an "S3 compatible" blobstore
# that doesn't support versioned blobs
# - timestamped filenames will need to be represented
# with a glob-style wildcard in tasks that use this state file
# (such as state-*.yml)
URL or GitHub link to the page where you're having the issue
https://github.com/pivotal/docs-platform-automation/blob/d3d106144126108e197f0aa7859c477b0eddb5b6/docs/examples/pipeline/pks/pipeline.yml
name: platform-automation-tasks
type: s3
source:
access_key_id: ((s3.access_key_id))
secret_access_key: ((s3.secret_access_key))
region_name: ((s3.region_name))
bucket: ((s3.buckets.pivnet_products))
regexp: .tasks-(.).zip
name: platform-automation-image
type: s3
source:
access_key_id: ((s3.access_key_id))
secret_access_key: ((s3.secret_access_key))
region_name: ((s3.region_name))
bucket: ((s3.buckets.pivnet_products))
regexp: .image-(.).tgz
these examples with dot but should have _
like here
URL or GitHub link to the page where you're having the issue
https://docs.pivotal.io/platform-automation/v4.3/how-to-guides/git-repo-layout.html
https://docs.pivotal.io/platform-automation/v4.3/pipeline-design/configuration-management-strategies.html
Is your request for a change or addition to content related to a problem? If so, please describe.
Each of these links has a recommendation for how to layout the configuration and they differ.
Describe the solution you'd like
It would be less confusing to a user if the recommendations where the same or pointed to the same page.
Describe alternatives you've considered
Additional context
Describe the bug
When using the configure-opsman task it will print the help for vm-lifecycle
before executing the proper commands successfully.
This is due to the om vm-lifecycle -v
call that can be found here
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The configure-opsman task to function without printing help unnecessarily or an unrelated command
Screenshots
N/A
selected worker: 0b2d37d2-740e-486f-8ddc-959672ba1b74
5.0.15
Usage:
om [OPTIONS] vm-lifecycle <command>
commands to manage the state of the Ops Manager VM. Requires the cli of the desired IAAS to be installed.
Application Options:
--ca-cert= OpsManager CA certificate path or value [$OM_CA_CERT]
-c, --client-id= Client ID for the Ops Manager VM (not required for unauthenticated commands) [$OM_CLIENT_ID]
-s, --client-secret= Client Secret for the Ops Manager VM (not required for unauthenticated commands) [$OM_CLIENT_SECRET]
-o, --connect-timeout= timeout in seconds to make TCP connections (default: 10) [$OM_CONNECT_TIMEOUT]
-d, --decryption-passphrase= Passphrase to decrypt the installation if the Ops Manager VM has been rebooted (optional for most commands) [$OM_DECRYPTION_PASSPHRASE]
-e, --env= env file with login credentials
-p, --password= admin password for the Ops Manager VM (not required for unauthenticated commands) [$OM_PASSWORD]
-r, --request-timeout= timeout in seconds for HTTP requests to Ops Manager (default: 1800) [$OM_REQUEST_TIMEOUT]
-k, --skip-ssl-validation skip ssl certificate validation during http requests [$OM_SKIP_SSL_VALIDATION]
-t, --target= location of the Ops Manager VM [$OM_TARGET]
--trace prints HTTP requests and response payloads [$OM_TRACE]
-u, --username= admin username for the Ops Manager VM (not required for unauthenticated commands) [$OM_USERNAME]
--vars-env= load vars from environment variables by specifying a prefix (e.g.: 'MY' to load MY_var=value) (default: OM_VAR) [$OM_VARS_ENV]
-v, --version prints the om release version
Help Options:
-h, --help Show this help message
Available commands:
create-vm Create VM for Ops Manager to a given IaaS
delete-vm Delete VM from a given IaaS
export-opsman-config Exports an opsman.yml for an existing Ops Manager VM
prepare-tasks-with-secrets Modifies task files to include config secrets as environment variables
upgrade-opsman Deletes the old opsman vm given an exported installation, bring up a new vm, and import that installation
+ vars_files_args=("")
+ for vf in ${VARS_FILES}
+ vars_files_args+=("--vars-file ${vf}")
+ for vf in ${VARS_FILES}
+ vars_files_args+=("--vars-file ${vf}")
...
(rest of the successful task here)
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
om --version
6516c1a327f7bb7ede88c857e5b4d0d58f27f5bc-2021-01-26T10:53:54-07:00
Concourse v6.7.1
Platform Automation v5.0.15
Collaborator added: pspinrad
URL or GitHub link to the page where you're having the issue
In the example files located here: https://docs.pivotal.io/platform-automation/v4.3/how-to-guides/configuring-auth.html#generating-an-auth-file
Is your request for a change or addition to content related to a problem? If so, please describe.
The client ID for the client referenced in precreated-client-secret
is ambiguous.
Describe the solution you'd like
Please add a comment that indicates that the client ID is precreated-client
URL or GitHub link to the page where you're having the issue
http://docs.pivotal.io/platform-automation/v3.0/reference/inputs-outputs.html#download-product-config
line 46 in the code block at the bottom
Is your request for a change or addition to content related to a problem? If so, please describe.
The code mentions s3-auth-method
when the actual flag is s3-auth-type
.
Describe the solution you'd like
Change s3-auth-method
to s3-auth-type
.
Describe alternatives you've considered
Additional context
I found the correct flag by running om download-product --help
with version 1.1.0.
$ om --version
1.1.0
$ om download-product --help
ॐ download-product
This command attempts to download a single product file from Pivotal Network. The API token used must be associated with a user account that has already accepted the EULA for the specified product
Usage: om [options] download-product [<args>]
--client-id, -c, OM_CLIENT_ID string Client ID for the Ops Manager VM (not required for unauthenticated commands)
--client-secret, -s, OM_CLIENT_SECRET string Client Secret for the Ops Manager VM (not required for unauthenticated commands)
--connect-timeout, -o, OM_CONNECT_TIMEOUT int timeout in seconds to make TCP connections (default: 10)
--decryption-passphrase, -d, OM_DECRYPTION_PASSPHRASE string Passphrase to decrypt the installation if the Ops Manager VM has been rebooted (optional for most commands)
--env, -e string env file with login credentials
--help, -h bool prints this usage information (default: false)
--password, -p, OM_PASSWORD string admin password for the Ops Manager VM (not required for unauthenticated commands)
--request-timeout, -r, OM_REQUEST_TIMEOUT int timeout in seconds for HTTP requests to Ops Manager (default: 1800)
--skip-ssl-validation, -k, OM_SKIP_SSL_VALIDATION bool skip ssl certificate validation during http requests (default: false)
--target, -t, OM_TARGET string location of the Ops Manager VM
--trace, -tr, OM_TRACE bool prints HTTP requests and response payloads
--username, -u, OM_USERNAME string admin username for the Ops Manager VM (not required for unauthenticated commands)
--version, -v bool prints the om release version (default: false)
Command Arguments:
--config, -c string path to yml file for configuration (keys must match the following command line flags)
--download-stemcell bool no-op for backwards compatibility
--output-directory, -o string (required) directory path to which the file will be outputted. File Name will be preserved from Pivotal Network
--pivnet-api-token, -t string (required) API token to use when interacting with Pivnet. Can be retrieved from your profile page in Pivnet.
--pivnet-disable-ssl bool whether to disable ssl validation when contacting the Pivotal Network
--pivnet-file-glob, -f string (required) glob to match files within Pivotal Network product to be downloaded.
--pivnet-product-slug, -p string (required) path to product
--product-version, -v string version of the product-slug to download files from. Incompatible with --product-version-regex flag.
--product-version-regex, -r string regex pattern matching versions of the product-slug to download files from. Highest-versioned match will be used. Incompatible with --product-version flag.
--s3-access-key-id string access key for the s3 compatible blobstore
--s3-auth-type string can be set to "iam" in order to allow use of instance credentials (default: accesskey)
--s3-bucket string bucket name where the product resides in the s3 compatible blobstore
--s3-disable-ssl bool whether to disable ssl validation when contacting the s3 compatible blobstore
--s3-enable-v2-signing bool whether to use v2 signing with your s3 compatible blobstore. (if you don't know what this is, leave blank, or set to 'false')
--s3-endpoint string the endpoint to access the s3 compatible blobstore. If not using AWS, this is required
--s3-product-path string specify the lookup path where the s3 product artifacts are stored. for example, "/location-name/" will look for files under s3://bucket-name/location-name/
--s3-region-name string bucket region in the s3 compatible blobstore. If not using AWS, this value is 'region'
--s3-secret-access-key string secret key for the s3 compatible blobstore
--s3-stemcell-path string specify the lookup path where the s3 stemcell artifacts are stored. for example, "/location-name/" will look for files under s3://bucket-name/location-name/
--source, -s string enables download from external sources when set to "s3". if not provided, files will be downloaded from Pivnet
--stemcell-iaas string download the latest available stemcell for the product for the specified iaas. for example 'vsphere' or 'vcloud' or 'openstack' or 'google' or 'azure' or 'aws'
--vars-env string (variadic) load variables from environment variables matching the provided prefix (e.g.: 'MY' to load MY_var=value)
--vars-file, -l string (variadic) load variables from a YAML file
URL or GitHub link to the page where you're having the issue
Where in the documentation set can I see the problem? If it's a more general request, then at least identify the product and version.
Is your request for a change or addition to content related to a problem? If so, please describe.
The documentation for using UAA authentication says "SAML" authentication
Describe the solution you'd like
It should say UAA authentication
Describe alternatives you've considered
n/a
Additional context
See the difference between the two links:
URL or GitHub link to the page where you're having the issue
https://docs.pivotal.io/platform-automation/v4.1/inputs-outputs.html#vsphere
https://github.com/pivotal/docs-platform-automation/blob/v4.1/docs/examples/opsman-config/vsphere.yml
Is your request for a change or addition to content related to a problem? If so, please describe.
hostname is DEPRECATED:
https://github.com/pivotal/platform-automation/blob/5a31a5a4ca1bdbc15d9a3e2ea941e281acfaab4b/pkg/vmmanagers/vsphere.go#L113
Describe the solution you'd like
We should modify the example to reflect the DEPRECATION of hostname.
Describe alternatives you've considered
none
Additional context
none
Describe the bug
When looking at a page, the hamburger menu does not "focus" on where the page is in the menu hierarchy. This confused me initially when exploring the breadth of the documentation.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expected to see the "References" sub-menu shown
Desktop (please complete the following information):
Additional context
Even more confusing, pressing the back button located in the menu itself does not traverse up the menu hierarchy to the root. Instead, it traverses linearly back through the sibling sub-menus.
Describe the bug
A clear and concise description of what the bug is.
When I land on v3 page and want to switch to v4 the page that is fetched is the default page instead of the v4 version of the page. For example if I'm looking at the download-product task reference and I want to see the v4 version of the page, I select the v4 drop down and I get directed to the root of the platform automation site.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect that when I navigate to a v3 page then switch to its v4 counterpart that I stay on the same page topic, even if the page has moved location.
Desktop (please complete the following information):
Additional context
n/a
NOTE: Public Repos are disabled for this organization! Repository was automatically converted to a Private Repo. Please contact an admin to override.
/cc @vtorres2
/cc @onlyawave @chadleyman
URL or GitHub link to the page where you're having the issue
Where in the documentation set can I see the problem? If it's a more general request, then at least identify the product and version.
Is your request for a change or addition to content related to a problem? If so, please describe.
A clear and concise description of the problem. For example: "Whenever I upgrade my software I forget to first collect information about the things I've already installed"
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or content you've considered.
Additional context
Add any other context or screenshots about the content request here.
`
fly -t control-plane set-pipeline
-p foundation
-c pipeline.yml
-v pivnet-refresh-token=your-api-token`
needs tom have content of -v in double quotes:
fly -t control-plane set-pipeline
-p foundation
-c pipeline.yml
-v "pivnet-refresh-token=your-api-token"
NOTE: Public Repos are disabled for this organization! Repository was automatically converted to a Private Repo. Please contact an admin to override.
/cc @vtorres2
/cc @onlyawave @chadleyman
NOTE: Public Repos are disabled for this organization! Repository was automatically converted to a Private Repo. Please contact an admin to override.
/cc @kcboyle
/cc @onlyawave @chadleyman
URL or GitHub link to the page where you're having the issue
The reference pipeline
Where in the documentation set can I see the problem? If it's a more general request, then at least identify the product and version.
Same as above. The future issue will be related to the Healthwatch install in the pipeline.
Is your request for a change or addition to content related to a problem? If so, please describe.
Both a change and an addition. The reference pipeline installs TAS, TKGI, and Healthwatch.
When Healthwatch 2.1 is released as GA (coming soon in March 2021), this will no longer be enough. Healthwatch 2.1 requires the install of Exporter tiles (one for TKGI, one for TAS) in order to report metrics on those installed tiles.
Describe the solution you'd like
update the reference pipeline and/or how-to guides to include the install of the exporter tiles when installing Healthwatch 2.1.
Describe alternatives you've considered
Additional context
URL or GitHub link to the page where you're having the issue
https://docs.pivotal.io/platform-automation/v4.0/pipelines/single-product.html#configured-resources
Is your request for a change or addition to content related to a problem? If so, please describe.
In v4 of the reference pipeline for Ops Manager + a product https://docs.pivotal.io/platform-automation/v4.0/pipelines/single-product.html#configured-resources the variable
state store was renamed to state
and the resource definition was removed. You can see how it was defined in v3 here: https://docs.pivotal.io/platform-automation/v3.0/pipeline/single-product.html#configured-resources . The reference pipeline now calls this resource state
but the user of the documentation is unaware that it is a git resource because the resource definition was removed.
Describe the solution you'd like
Add the definition for the state resource back:
- name: state
type: git
source:
private_key: ((state.private_key))
uri: ((state.uri))
branch: master
Describe alternatives you've considered
n/a
Additional context
n/a
Describe the bug
The task reference documentation, which very conveniently has the ability to copy the whole block of a task or shell script, is missing the shebang (#!
) for all of the task sh files
To Reproduce
Steps to reproduce the behavior:
Implementation
Expected behavior
The shebangs will be present
Additional context
The code_snippet
comments can be moved above the shebang to fix the problem. I will look into providing a PR fix.
URL or GitHub link to the page where you're having the issue
Is your request for a change or addition to content related to a problem? If so, please describe.
Feature Request.
Describe the solution you'd like
Updates to the apply-changes task to allow a pipeline developer to override the default (all) products that changes are applied.
Describe alternatives you've considered
None
Describe the bug
An unintuitive permission is necessary for the GCP upgrade process:
compute.images.delete
.
This is included in "Compute Instance Admin (v1)" - compute.instanceAdmin
- which the Ops Manager docs list as required. This is likely the only required permission for the Ops Manager VM and image management parts of Platform Automation; others may be necessary depending on blob store selection.
Currently, the Platform Automation docs don't list necessary permission prerequisites on GCP at all. They should! Not sure exactly where, yet.
The Paving repo docs list permissions necessary for setup of environments, which includes instanceAdmin:
https://github.com/pivotal/paving/tree/master/gcp
Those permissions are broader than what PA requires, but cover the additional permissions necessary to setup the envs Paving operates in, so may also be of interest.
The following section in the documentation ....
'''
download-product
Downloads a product specified in a config file from an S3-compatible blobstore. This is useful when retrieving assets in an offline environment.
Downloads are cached, so files are not re-downloaded each time.
This is intended to be used with files downloaded from Pivnet by download-product and then persisted to a blobstore using a put step.
'''
Please provide an example of a "put" to store to S3.
As far as I can discern from the code, the write to S3 is a function of the config.yaml that is passed to the download-product task and NOT from a put directive.
I'd like to see some clear examples of download-product (and stemcells) that store to S3 for future download from s3. (air-gapped environment).
The documentation should include some clear examples for customers in an air-gapped environment (no direct connection to pivnet).
URL or GitHub link to the page where you're having the issue
https://docs.pivotal.io/platform-automation/v3.0/pipeline/multiple-products.html#jobs
Is your request for a change or addition to content related to a problem? If so, please describe.
The formatting is off where multiple lines have incorrect whitespace prefixing. The most notable are the individual tasks are tabbed to the right.
Describe the solution you'd like
Here is the corrected pipeline
jobs:
- name: test-platform-automation
serial: true
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- task: test-interpolate
image: platform-automation-image
file: platform-automation-tasks/tasks/test-interpolate.yml
params:
CONFIG_FILE: download-product-configs/pas.yml
SKIP_MISSING: true
input_mapping:
config: configuration
- task: test
file: platform-automation-tasks/tasks/test.yml
image: platform-automation-image
- name: delete-opsman
serial: true
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- get: state
- task: interpolate-creds
<<: *interpolate-creds
- task: delete-installation
image: platform-automation-image
file: platform-automation-tasks/tasks/delete-installation.yml
input_mapping:
env: interpolated-creds
- task: delete-vm
image: platform-automation-image
file: platform-automation-tasks/tasks/delete-vm.yml
input_mapping:
config: interpolated-creds
- put: state
params:
file: generated-state/state.yml
- name: install-opsman
serial: true
serial_groups: [ install ]
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
- get: one-time-trigger
trigger: true
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- get: state
- task: interpolate-creds
<<: *interpolate-creds
- task: download-opsman-image
image: platform-automation-image
file: platform-automation-tasks/tasks/download-product-s3.yml
params:
CONFIG_FILE: download-product-configs/opsman.yml
input_mapping:
config: interpolated-creds
output_mapping:
downloaded-product: opsman-image
- task: create-vm
image: platform-automation-image
file: platform-automation-tasks/tasks/create-vm.yml
input_mapping:
image: opsman-image
config: interpolated-creds
ensure: &put-state
do:
- put: state
params:
file: state/state.yml
- task: configure-authentication
image: platform-automation-image
file: platform-automation-tasks/tasks/configure-authentication.yml
attempts: 10
input_mapping:
env: interpolated-creds
config: interpolated-creds
- task: configure-director
image: platform-automation-image
file: platform-automation-tasks/tasks/configure-director.yml
input_mapping:
config: interpolated-creds
env: interpolated-creds
- task: apply-director-changes
image: platform-automation-image
file: platform-automation-tasks/tasks/apply-director-changes.yml
input_mapping:
env: interpolated-creds
- name: staged-director-config
serial: true
plan:
- aggregate:
- get: platform-automation-tasks
params: {unpack: true}
- get: platform-automation-image
params: {unpack: true}
- get: configuration
- get: state
- task: interpolate-creds
<<: *interpolate-creds
- task: staged-director-config
image: platform-automation-image
file: platform-automation-tasks/tasks/staged-director-config.yml
input_mapping:
env: interpolated-creds
ensure: *put-state
- name: export-installation
serial: true
plan:
- aggregate:
- get: daily-trigger
trigger: true
- get: platform-automation-image
params:
unpack: true
passed: [ install-opsman ]
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- get: one-time-trigger
passed: [ install-opsman ]
- task: interpolate-creds
<<: *interpolate-creds
- task: export-installation
image: platform-automation-image
file: platform-automation-tasks/tasks/export-installation.yml
input_mapping:
env: interpolated-creds
params:
INSTALLATION_FILE: installation-$timestamp.zip
- put: installation
params:
file: installation/installation*.zip
- name: upgrade-opsman
serial: true
serial_groups: [ install ]
plan:
- aggregate:
- get: one-time-trigger
passed: [ export-installation ]
- get: platform-automation-image
params:
unpack: true
trigger: true
- get: platform-automation-tasks
params:
unpack: true
- get: installation
passed: [ export-installation ]
- get: configuration
- get: state
- task: interpolate-creds
<<: *interpolate-creds
- task: download-opsman-image
image: platform-automation-image
file: platform-automation-tasks/tasks/download-product-s3.yml
params:
CONFIG_FILE: download-product-configs/opsman.yml
input_mapping:
config: interpolated-creds
output_mapping:
downloaded-product: opsman-image
- task: upgrade-opsman
image: platform-automation-image
file: platform-automation-tasks/tasks/upgrade-opsman.yml
input_mapping:
image: opsman-image
config: interpolated-creds
env: interpolated-creds
ensure: *put-state
- task: configure-director
image: platform-automation-image
file: platform-automation-tasks/tasks/configure-director.yml
input_mapping:
config: interpolated-creds
env: interpolated-creds
- task: apply-director-changes
image: platform-automation-image
file: platform-automation-tasks/tasks/apply-director-changes.yml
input_mapping:
env: interpolated-creds
- name: upload-and-stage-pas
serial: true
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
passed:
- upgrade-opsman
trigger: true
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- task: interpolate-creds
<<: *interpolate-creds
- task: download-pas
image: platform-automation-image
file: platform-automation-tasks/tasks/download-product-s3.yml
params:
CONFIG_FILE: download-product-configs/pas.yml
input_mapping:
config: interpolated-creds
output_mapping:
downloaded-product: pas-product
downloaded-stemcell: pas-stemcell
- task: upload-product
image: platform-automation-image
file: platform-automation-tasks/tasks/upload-product.yml
input_mapping:
product: pas-product
env: interpolated-creds
- task: upload-pas-stemcell
image: platform-automation-image
file: platform-automation-tasks/tasks/upload-stemcell.yml
input_mapping:
env: interpolated-creds
stemcell: pas-stemcell
- task: stage-product
image: platform-automation-image
file: platform-automation-tasks/tasks/stage-product.yml
input_mapping:
product: pas-product
env: interpolated-creds
- name: configure-pas
serial: true
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
passed:
- upload-and-stage-pas
trigger: true
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- task: interpolate-creds
<<: *interpolate-creds
- task: configure-pas
image: platform-automation-image
file: platform-automation-tasks/tasks/configure-product.yml
input_mapping:
config: interpolated-creds
env: interpolated-creds
params:
CONFIG_FILE: cf.yml
- name: upload-and-stage-pas-windows
serial: true
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
passed:
- upgrade-opsman
trigger: true
- get: platform-automation-tasks
params:
unpack: true
- get: pas-windows-product
- get: pas-windows-stemcell
- get: configuration
- task: interpolate-creds
<<: *interpolate-creds
- task: upload-product
image: platform-automation-image
file: platform-automation-tasks/tasks/upload-product.yml
input_mapping:
product: pas-windows-product
env: interpolated-creds
- task: upload-pas-windows-stemcell
image: platform-automation-image
file: platform-automation-tasks/tasks/upload-stemcell.yml
input_mapping:
env: interpolated-creds
stemcell: pas-windows-stemcell
- task: stage-product
image: platform-automation-image
file: platform-automation-tasks/tasks/stage-product.yml
input_mapping:
product: pas-windows-product
env: interpolated-creds
- name: configure-pas-windows
serial: true
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
passed:
- upload-and-stage-pas-windows
trigger: true
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- task: interpolate-creds
<<: *interpolate-creds
- task: configure-pas
image: platform-automation-image
file: platform-automation-tasks/tasks/configure-product.yml
input_mapping:
config: interpolated-creds
env: interpolated-creds
params:
CONFIG_FILE: pas-windows.yml
- name: upload-and-stage-healthwatch
serial: true
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
trigger: true
passed: [ "upgrade-opsman" ]
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- task: interpolate-creds
<<: *interpolate-creds
- task: download-healthwatch
image: platform-automation-image
file: platform-automation-tasks/tasks/download-product-s3.yml
params:
CONFIG_FILE: download-product-configs/healthwatch.yml
input_mapping:
config: interpolated-creds
output_mapping:
downloaded-product: healthwatch-product
downloaded-stemcell: healthwatch-stemcell
- task: upload-and-stage-product
image: platform-automation-image
file: platform-automation-tasks/tasks/upload-and-stage-product.yml
input_mapping:
product: healthwatch-product
env: interpolated-creds
- task: upload-healthwatch-stemcell
image: platform-automation-image
file: platform-automation-tasks/tasks/upload-stemcell.yml
input_mapping:
env: interpolated-creds
stemcell: healthwatch-stemcell
- name: configure-healthwatch
serial: true
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
passed:
- upload-and-stage-healthwatch
trigger: true
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- task: interpolate-creds
<<: *interpolate-creds
- task: configure-healthwatch
image: platform-automation-image
file: platform-automation-tasks/tasks/configure-product.yml
input_mapping:
config: interpolated-creds
env: interpolated-creds
params:
CONFIG_FILE: healthwatch.yml
- name: apply-product-changes
serial: true
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
passed:
- configure-healthwatch
- configure-pas
- configure-pas-windows
trigger: true
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- task: interpolate-creds
<<: *interpolate-creds
- task: pre-deploy-check
image: platform-automation-image
file: platform-automation-tasks/tasks/pre-deploy-check.yml
input_mapping:
env: interpolated-creds
- task: apply-product-changes
image: platform-automation-image
file: platform-automation-tasks/tasks/apply-changes.yml
input_mapping:
env: interpolated-creds
- name: staged-pas-config
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- get: state
- task: interpolate-creds
<<: *interpolate-creds
- task: staged-config
image: platform-automation-image
file: platform-automation-tasks/tasks/staged-config.yml
input_mapping:
env: interpolated-creds
params:
PRODUCT_NAME: cf
ensure: *put-state
- name: staged-healthwatch-config
plan:
- aggregate:
- get: platform-automation-image
params:
unpack: true
- get: platform-automation-tasks
params:
unpack: true
- get: configuration
- get: state
- task: interpolate-creds
<<: *interpolate-creds
- task: staged-config
image: platform-automation-image
file: platform-automation-tasks/tasks/staged-config.yml
input_mapping:
env: interpolated-creds
params:
PRODUCT_NAME: p-healthwatch
ensure: *put-state
Describe alternatives you've considered
n/a
Additional context
n/a
URL or GitHub link to the page where you're having the issue
https://docs.pivotal.io/platform-automation/v4.3/pipelines/resources.html#platform-automation-resources
- name: platform-automation-pivnet
type: pivnet
source:
api_token: ((pivnet_token))
product_slug: platform-automation
product_version: 2\.(.*)
sort_by: semver
Is your request for a change or addition to content related to a problem? If so, please describe.
2.x.x version does not exist in pivnet. And so product_version: 2.(.*) makes that the concourse downloads 4.2.3 version currently.
But 4.2.3 version of platform-automation-tasks does not have prepare-tasks-with-secrets.yml and so file not found error is occurred.
Describe the solution you'd like
I hope to change product_version from 2.(.) to 4.(.). After this change, it works.
NOTE: Public Repos are disabled for this organization! Repository was automatically converted to a Private Repo. Please contact an admin to override.
/cc @kcboyle
/cc @onlyawave @chadleyman
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.