-
Notifications
You must be signed in to change notification settings - Fork 244
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allow using remote Dockerfiles (HTTP(S) only) for building images (#5976
) * Add utility function in `docker_compatible.go` allowing to resolve a Dockerfile For now, this only supports HTTP(S) and downloads the remote file to a temporary file. The path to that temp. file is then returned to the caller. In all other cases, the specified URI path is returned as is. This means that non-HTTP(S) URIs will *not* get resolved, but will be returned as is. Signed-off-by: Armel Soro <asoro@redhat.com> * Allow using remote HTTP(S) Dockerfiles with both `deploy` and `build-images` commands Signed-off-by: Armel Soro <asoro@redhat.com> * Join resolved Dockerfile path with the Devfile one only if the former is relative It actually does not make sense to join absolute Dockerfile paths, as can be the case with temporary files created by downloading a remote Dockerfile Signed-off-by: Armel Soro <asoro@redhat.com> * Add integration test cases for `odo build-images` Signed-off-by: Armel Soro <asoro@redhat.com> * Add integration test cases for `odo deploy` Signed-off-by: Armel Soro <asoro@redhat.com> * Update doc for both `build-images` and `deploy` commands Signed-off-by: Armel Soro <asoro@redhat.com> * fixup! Add utility function in `docker_compatible.go` allowing to resolve a Dockerfile * fixup! Allow using remote HTTP(S) Dockerfiles with both `deploy` and `build-images` commands Signed-off-by: Armel Soro <asoro@redhat.com> * fixup! Allow using remote HTTP(S) Dockerfiles with both `deploy` and `build-images` commands * fixup! 878285b
- Loading branch information
Showing
14 changed files
with
413 additions
and
50 deletions.
There are no files selected for viewing
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,14 @@ | ||
package deploy | ||
|
||
import "github.com/devfile/library/pkg/devfile/parser" | ||
import ( | ||
"github.com/devfile/library/pkg/devfile/parser" | ||
|
||
"github.com/redhat-developer/odo/pkg/testingutil/filesystem" | ||
) | ||
|
||
type Client interface { | ||
// Deploy resources from a devfile located in path, for the specified appName | ||
Deploy(devfileObj parser.DevfileObj, path string, appName string) error | ||
// Deploy resources from a devfile located in path, for the specified appName. | ||
// The filesystem specified is used to download and store the Dockerfiles needed to build the necessary container images, | ||
// in case such Dockerfiles are referenced as remote URLs in the Devfile. | ||
Deploy(fs filesystem.Filesystem, devfileObj parser.DevfileObj, path string, appName string) error | ||
} |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
Oops, something went wrong.