Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch Admin API to Use Task/TaskRun Instead of Workflow API #1729

Open
cjellick opened this issue Feb 12, 2025 · 0 comments
Open

Switch Admin API to Use Task/TaskRun Instead of Workflow API #1729

cjellick opened this issue Feb 12, 2025 · 0 comments
Assignees

Comments

@cjellick
Copy link
Contributor

cjellick commented Feb 12, 2025

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:

  1. Expose the task and taskrun API for admin use.
  2. 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.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants