github.com/replicatedhq/ship@v0.55.0/integration/base/basic/input/.ship/ship.yml (about) 1 2 --- 3 # assets are everything an end customer needs to deploy your application, like 4 # 5 # - kubernetes or docker-compose manifests 6 # - installation scripts 7 # - modules for ansible/chef/puppet 8 # - private docker images 9 # - compiled artifacts and binaries 10 # 11 # assets will be templated using customer-supplied 12 # install info from the "config" section (below) 13 assets: 14 v1: 15 # "inline" can be used to supply assets directly in the spec 16 - inline: 17 contents: | 18 #!/bin/bash 19 echo "installing nothing" 20 echo "config option: {{repl ConfigOption "test_option" }}" 21 dest: ./scripts/install.sh 22 mode: 0777 23 - inline: 24 contents: | 25 #!/bin/bash 26 echo "tested nothing" 27 dest: ./scripts/test.sh 28 mode: 0777 29 30 # "docker" can be used to provide proxied access to private docker images 31 # - docker: 32 # image: postgres 33 # source: public 34 # dest: docker/postgres.tar 35 36 # Config defines the configuration options available to your application. 37 # Values supplied by the end customer will be used during asset generation. 38 config: 39 v1: 40 - name: test_options 41 title: Test Options 42 description: testing testing 123 43 items: 44 - name: test_option 45 title: Test Option 46 type: text 47 48 # Lifecycle allows you to customize the messaging and workflow for your end customer 49 # when they are generating assets. Currently the two support lifecycle steps are 50 # 51 # - message -- prints a message 52 # - render -- collects config and generates assets 53 lifecycle: 54 v1: 55 - render: {} 56