service can use x-* name #413
Conversation
Signed-off-by: Nicolas De Loof <[email protected]>
There was a problem hiding this comment.
From a semantic point of view that looks confusing to have a service prefixed with x- and I ask myself if we should or not allow it given that it has a meaning in other parts of the file.
From a technical point, YES... Why not? Makes sense that we would not use x- in the services map.
The question is... Do we want that to have this "ambiguity"?
A huge majority of compose users don't rely on extensions (many don't know about yaml anchors), but use a simple compose.yaml file. But within those there's a significant amount of our users who might have service named Also, this is not a new feature, just a fix for incomplete #255 which was discussed 1 year ago :P |
extensions are not supported inside the
servicestop-level attribute, this allows users to declare services with name starting byx-...Unfortunately support for this is buggy, and here is a fix + test-case :)closes docker/compose#8809