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
Summary:
The current admin API uses the workflow API, which makes it difficult to view parameters passed to a task. It is proposed to switch the admin API to use the task and taskrun API that exists for users, allowing for better visibility and management of task parameters.
Details:
The task and taskrun API should be exposed on the admin side.
This change will allow the admin to see the same information as the user side, improving transparency and usability.
The workflowexecution type has the input on it, but the admin API doesn't currently show this. Switching to task/taskrun will address this issue.
Action Items:
Expose the task and taskrun API for admin use.
Fully switch the admin over to these APIs, moving away from the workflow API.
Additional Notes:
This change should be fairly simple as the APIs already exist.
Consideration should be given to how this change will impact existing workflows and integrations.
This issue was created based on a discussion in the engineering Slack channel. If there are any questions or further clarifications needed, please refer to the original thread or contact Craig Jellick or Darren Shepherd.
Note: This issue was created with the assistance of AI to summarize the discussion.
The text was updated successfully, but these errors were encountered:
Summary:
The current admin API uses the workflow API, which makes it difficult to view parameters passed to a task. It is proposed to switch the admin API to use the task and taskrun API that exists for users, allowing for better visibility and management of task parameters.
Details:
Action Items:
Additional Notes:
References:
This issue was created based on a discussion in the engineering Slack channel. If there are any questions or further clarifications needed, please refer to the original thread or contact Craig Jellick or Darren Shepherd.
Note: This issue was created with the assistance of AI to summarize the discussion.
The text was updated successfully, but these errors were encountered: