Replies: 1 comment
-
Interesting - to me that sounds like a pattern that is best enforced through permissions, not business logic. What's the business logic/use case motivation for such a constraint? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
x-posted from community.
Denying manual invocations of a deployment takes work, like inspecting the invocation a la
get_client
and failing it if it doesn't contain anauto-scheduled
tag. Pausing a deployment shuts off all invocation methods, so there isn't a happy path for someone who wants to run code only on a schedule.Idea: Allow a user to disable all manual invocations of a deployment while still allowing temporal/automation-based triggers.
Beta Was this translation helpful? Give feedback.
All reactions