time="2015-06-11T23:32:27Z" level=info msg="-job log(pull, deis/builder:v1.7.2, ) = OK (0)"
Jun 11 23:32:27 deis-02 docker[1083]: time="2015-06-11T23:32:27Z" level=info msg="-job pull(deis/builder, v1.7.2) = OK (0)"
Jun 11 23:32:27 deis-02 docker[1083]: time="2015-06-11T23:32:27Z" level=info msg="GET /v1.18/containers/deis-builder/json"
Jun 11 23:32:27 deis-02 docker[1083]: time="2015-06-11T23:32:27Z" level=info msg="+job container_inspect(deis-builder)"
Jun 11 23:32:27 deis-02 docker[1083]: no such id: deis-builder
Jun 11 23:32:27 deis-02 docker[1083]: time="2015-06-11T23:32:27Z" level=info msg="-job container_inspect(deis-builder) = ERR (1)"
Jun 11 23:32:27 deis-02 docker[1083]: time="2015-06-11T23:32:27Z" level=error msg="Handler for GET /containers/{name:.*}/json returned error: no such id: deis-builder"
Jun 11 23:32:27 deis-02 docker[1083]: time="2015-06-11T23:32:27Z" level=error msg="HTTP Error: statusCode=404 no such id: deis-builder"
Jun 11 23:32:27 deis-02 docker[1083]: time="2015-06-11T23:32:27
I hereby claim:
- I am kmala on github.
- I am kmala (https://keybase.io/kmala) on keybase.
- I have a public key whose fingerprint is 9C3C 1DF2 34AE 8CB8 130C 4201 021C 6FC9 DDF7 9D3C
To claim this, I am signing this object:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Deis CLI : | |
old requestbody: | |
{ | |
"readiness":{} | |
"liveness": {} | |
} | |
new requestbody: | |
{ | |
"type": { | |
"readiness":{} |
7fbeb3f
router: move deis-router to use Deployments69831ed
workflow-manager: move deis-workflow-manager to use Deployments31cbcc9
registry: move deis-registry to use Deployments4173034
controller: move deis-controller to use Deployments106e022
builder: move deis-builder to use Deployments1692748
test: add TEST env variable to workflow e2e chart78e77cb
workflow-dev: re-introduce
#Install
Workflow [2.3.0][chart2.3.0] and [2.4.1][chart2.4.1] can be installed using the new helm and can do the same customizations of the components/storage as helm-classic.The customizations are applied in a cleaner way than helm-classic where we had a shell script. The install process is also the same as helm-classic, you fetch a chart using helm fetch
then change the default values for customizations and helm install
.
##Different from helm-classic
- Users can longer use environment variables to set values for customizations.(helm/helm#944)
#Composable