Commit Graph

2 Commits

Author SHA1 Message Date
7b6cc4d6de fix stack path resolution
Some checks failed
Lint Checks / Run linter (pull_request) Failing after 36s
K8s Deploy Test / Run deploy test suite on kind/k8s (pull_request) Failing after 2m54s
Deploy Test / Run deploy test suite (pull_request) Failing after 4m3s
Webapp Test / Run webapp test suite (pull_request) Successful in 4m33s
Smoke Test / Run basic test suite (pull_request) Successful in 4m3s
This was broken for "build-containers" with external stacks. Now setup and build use the same functions.
2024-07-02 20:13:29 +08:00
da1ff609fe fetch-images command (#768)
All checks were successful
Lint Checks / Run linter (push) Successful in 35s
Publish / Build and publish (push) Successful in 1m33s
Webapp Test / Run webapp test suite (push) Successful in 3m44s
Smoke Test / Run basic test suite (push) Successful in 4m9s
Deploy Test / Run deploy test suite (push) Successful in 7m3s
Implementation of a command to fetch pre-built images from a remote registry, complementing the --push-images option already present on build-containers.

The two subcommands used together allow a stack to be deployed without needing to built its images, provided they have been already built and pushed to the specified container image registry.

This implementation simply picks the newest image with the right name and platform (matches against the platform Python is running on, so watch out for scenarios where Python is an x86 binary on M1 macs).

Reviewed-on: #768
Co-authored-by: David Boreham <david@bozemanpass.com>
Co-committed-by: David Boreham <david@bozemanpass.com>
2024-02-27 15:15:08 +00:00