github.com/replicatedhq/ship@v0.55.0/integration/base/docker/expected/.ship/release.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      - docker:
    30          image: replicated/helloscratch:1.0.0
    31          source: public
    32          dest: docker/hello.tar
    33  
    34      # "docker" can be used to provide proxied access to private docker images
    35  #    - docker:
    36  #        image: postgres
    37  #        source: public
    38  #        dest: docker/postgres.tar
    39  
    40  # Config defines the configuration options available to your application.
    41  # Values supplied by the end customer will be used during asset generation.
    42  config:
    43    v1:
    44      - name: test_options
    45        title: Test Options
    46        description: testing testing 123
    47        items:
    48        - name: test_option
    49          title: Test Option
    50          type: text
    51  
    52  # Lifecycle allows you to customize the messaging and workflow for your end customer
    53  # when they are generating assets. Currently the two support lifecycle steps are
    54  #
    55  #  - message -- prints a message
    56  #  - render  -- collects config and generates assets
    57  lifecycle:
    58    v1:
    59      - render: {}