-
Notifications
You must be signed in to change notification settings - Fork 118
bosh deploy manifest/cfcr.yml doesn't "just work" #279
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/155998950 The labels on this github issue will be updated when the story is started. |
+1000, i keep on having problem wiht this as well. preferable let's update with compiled releases. |
Hey @drnic / @cppforlife, given that CFCR is still pre-1.0 and that things are still fairly fluid, the team discussed postponing making this commitment for a bit longer. I personally think this is a good pattern, but it could lead to several issues if enabled today. An example of that is #287. cc @karampok |
At CF Summit I'm giving a talk based around the PR I did last year and the 'it just works' concept for BOSH operators. I understand that your priorities aren't my CF Summit talk :) So, I spent yesterday + today and came up with CI pipeline to pre-compile everything (except bosh-dns 0.2.0 which fails) and reconstruct a new Give the following one-liner a go:
|
There is no big difference between downloading / uploading a tarball and specifying URL to this tarball in manifest as under the hood bosh cli is doing the same thing. Can somebody clarify why cannot we just add the following to the manifest?
|
All that is required is a step in CI to update cfcr.yml Some sample scripts to do this are in https://github.com/starkandwayne/pipeline-templates/tree/master/boshrelease |
Starting from now on, master branch will be always deployable 🎉 |
kubo-deployment/manifests/cfcr.yml Lines 186 to 190 in 1a80fb3
Great work! |
…cubator#279) * Enable encryption config yaml file * Making encryption-config optional
As per manifests/README.md:
Can we please start automatically updating cfcr.yml with the latest kubo + other release versions?
The text was updated successfully, but these errors were encountered: