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
In general, I think we should reach feature parity between the spin CLI and the spin shim. A table that documents what features are implemented / not implemented is going to be useful
The text was updated successfully, but these errors were encountered:
I lean more toward K8s for scheduling cron jobs vs using an always running Spin application to run the job. However, I might be missing some benefit of using Spin's cron functionality rather than K8s. Is there a use case that the Spin cron trigger would make more sense than using K8s constructs?
I don't think we want to use K8s cron for this since running a spin app pod is the equivalent of a spin up. Running spin up on a cron basis wouldn't produce a result. Rather, we may want to support triggering a running app on a cron basis.
For more info: https://github.com/fermyon/spin-trigger-cron
In general, I think we should reach feature parity between the spin CLI and the spin shim. A table that documents what features are implemented / not implemented is going to be useful
The text was updated successfully, but these errors were encountered: