Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix use case of bosh-deploy-with-created-release task #139

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Commits on Nov 17, 2022

  1. Fix bosh-deploy-with-created-release task

    Task was not able to deploy a release, which was provided as a tarball. The task was looking for a final.yml,
    which is not present, when providing a tarball.
    Added a parameter to the task, to let the user provide a release-name for the tarball.
    svkrieger committed Nov 17, 2022
    Configuration menu
    Copy the full SHA
    8e151d4 View commit details
    Browse the repository at this point in the history
  2. Enable to deploy non-base release

    The task bosh-deploy-with-created-release failed in the shared function `bosh interpolate`.
    Reason is that the generated ops-file does not use `?` to allow for non-existent release in cf-deployment.yml
    svkrieger committed Nov 17, 2022
    Configuration menu
    Copy the full SHA
    1f36878 View commit details
    Browse the repository at this point in the history

Commits on Dec 8, 2022

  1. Make release version configurable in case of tarball release

    Bosh expects the version field to be set, even when deploying from a local path.
    svkrieger committed Dec 8, 2022
    Configuration menu
    Copy the full SHA
    1b1ecf2 View commit details
    Browse the repository at this point in the history