Skip to content

[No-Code] Include tasks/triggers in topology even if some required properties are not fully configured yet #8920

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

Open
anna-geller opened this issue May 22, 2025 · 1 comment
Labels
area/backend Needs backend code changes bug Something isn't working

Comments

@anna-geller
Copy link
Member

Describe the issue

Ideally, adding a new task and specifying a type should already make the topology show that task/trigger in the topology

@Skraye do you have an idea how we could handle this? (you're topology generation pro hence asking)

Current state:

Image

Environment

  • Kestra Version: develop
@anna-geller anna-geller added bug Something isn't working area/backend Needs backend code changes labels May 22, 2025
@github-project-automation github-project-automation bot moved this to Backlog in Issues May 22, 2025
@anna-geller anna-geller changed the title Include tasks/triggers in topology even if some required properties are not fully configured yet [No-Code] Include tasks/triggers in topology even if some required properties are not fully configured yet May 22, 2025
@Skraye
Copy link
Member

Skraye commented May 22, 2025

One of the cons of the topology is that we need a valid flow to generate the topology, here as your task is invalid, the flow isn't generated

One solution would be to create lightweight classes ( or check what we already have) to generate the topology with just the minimal properties

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backend Needs backend code changes bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

2 participants