gateway: enable named contexts for gateway frontend#3633
Conversation
|
I think we might need to modify some of the caps detection logic as well - I gave this a spin on a frontend that doesn't have the Even though my frontend doesn't use build-contexts, because of the propagation of build-contexts, the frontend needs to declare the cap. |
Not sure I understand. Isn't it correct that if the user passes |
|
Because with this patch we can determine the frontend based on the build-context, if you want to use this feature to only change the frontend, that frontend must support build-contexts, or it's propagated through, and immediately errors. |
|
I think it is just something we need to accept that if you wish to use |
813f401 to
5c9dd2a
Compare
jedevc
left a comment
There was a problem hiding this comment.
LGTM, but can we also get a test 👀
f6fdcdd to
5bd4955
Compare
Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
|
Testing this would mean building a custom frontend inside the test. Gateway testing is specific to Dockerfile frontend atm and is built into the test script that loads the frontend image. |
5bd4955 to
c5b354f
Compare
This allows overwriting the definition of
#syntaxnames same as can be done with other dockerfile names.Signed-off-by: Tonis Tiigi tonistiigi@gmail.com