You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
I'm frustrated in wasm dev mode when I want to push/deploy iterations of wasm filters with the same version. When I'm in dev mode, I don't want to have to bump the version number on every iteration. However, if I don't do that, Gloo Edge continues to use its latest cached version of that filter with the same version number. Even when I undeploy/deploy the filter, it still uses the cached version rather than fetching the latest from the OCI repo.
Describe the solution you'd like
I'd like support for the latest tag as in docker, quay, etc.
% wasme deploy gloo webassemblyhub.io/jameshbarton/bad-char-bug:latest --id=bad-char-bug
Error: All attempts fail:
#1: webassemblyhub.io/jameshbarton/bad-char-bug:latest: not found
Describe alternatives you've considered
Creating new versions for every iteration is a clunky workaround.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
I'm frustrated in wasm dev mode when I want to push/deploy iterations of wasm filters with the same version. When I'm in dev mode, I don't want to have to bump the version number on every iteration. However, if I don't do that, Gloo Edge continues to use its latest cached version of that filter with the same version number. Even when I undeploy/deploy the filter, it still uses the cached version rather than fetching the latest from the OCI repo.
Related to solo-io/gloo#4207
Describe the solution you'd like
I'd like support for the
latest
tag as in docker, quay, etc.Describe alternatives you've considered
Creating new versions for every iteration is a clunky workaround.
The text was updated successfully, but these errors were encountered: