https://www.puppet.com/community logo
Join Slack
Powered by
This message was deleted.
# puppet-enterprise
s
This message was deleted.
s
It’s an artifact of (now scuttled) work around project plans. Needless to say, if we were to do a greenfield redesign of the orchestrator API, things would be a bit different 😉
the idea of what the orchestrator should do has evolved significantly since the original “application orchestration” idea
b
does that mean one of them might go away in future releases? what's the recommended API endpoint to start a PE plan?
all this command vs job vs plan is a bit.. confusing 😄
s
IIRC, 
environment_plan_run
is newer and 
plan_run
would be the deprecation target, but I’ll confirm (and I don’t think that’s imminent)
the command endpoints are for actions that might take an indeterminant amount of time, like firing off a task, the 
/jobs
, 
/tasks
, 
/plan_jobs
endpoints are for listing results and other stored things like scheduled jobs
but the organization is definitely not perfect
and I get the confusion
we should add an explanation of that separation to the API docs
b
I think it's really confusing that those three only support GET and no POST/PUT
s
gotcha, so just looked, 
/plan_run
has not been marked deprecated so that’s safe for quite a while. We are good about long notice for things going away, perhaps too good 😉
b
😄
thanks for checking
s
de nada
b
btw, any chance we get a search bar for the plan history in the PE console, like we have it for the task history?
s
for name, yeah, we should do that - I’ll suggest
it’s already available in the API
I’d like to get 
userdata
match too
b
oh yes
s
that’s a slightly bigger lift as it’s not yet in the API
Open in Slack
PreviousNext
Powered by