Hi Geoff-
That's exactly the type of thing I was thinking.
I'd probably go with an "format" API parameter rather than a header
since it isn't a standard MIME type but that's a detail.
For deployments you are correct, the registered transformer for the
service would have to be able to tell
Hi Alex,
That certainly sounds like an interesting idea. I'm not entirely sure
I've got my head round it though. I guess I can see how you could add
a new type to the catalog, say by posting a Dockerfile as the request
body and having an API (HTTP) header of `x-brooklyn-type: dockerfile`.
In this
Hi Brooklyners,
Since the Catalog was overhauled many years ago with the TypeRegistry
approach, we have had support in the back-end for custom types and for
custom plan formats. The former is useful e.g. if you want to add a new
type to be used as a config key or initializer. The latter is
