tmctl dump - Add support for Docker-Compose & DigitalOcean#197
tmctl dump - Add support for Docker-Compose & DigitalOcean#197FranBarrera merged 21 commits intotriggermesh:mainfrom
Conversation
|
it works. but for DO:
|
|
Can you remove the For compose the full gcr.io/triggermesh name is correct. |
|
@sebgoa DO issues should be fine now |
|
This could be a follow on ticket. When there are more than one services (i.e targets) each should have its own route (instead of being just root /) and this should get reflected in the broker config if need be. |
|
A bit dirty but I am putting a diff here so that I don't loose it |
sebgoa
left a comment
There was a problem hiding this comment.
first functionality is there. so I am approving.
thanks for switching the transformation to a ServiceSpec
|
Looks like I cannot merge my branch with this PR because it is based on the personal fork. @FranBarrera could you cherry-pick 3017928? Alternatively, we can merge this one and then mine on the top, but cherry-picking is preferable to keep the change history clean. |
Added a new parameter to tmctl dump [--platform| -p] with multiple platforms [kubernetes | knative | docker-compose | digitalocean]. By default is kubernetes.
Example: