Problem
#1381 asks for a way to hide the complexity of creating importers from trigger creators for the simplest scenarios. One downside is that the ready status of hidden objects is also hidden: if an importer created on behalf of a user's trigger creation request fails to become ready, the user isn't able to easily determine that the importer is unready.
One way to solve this is to allow the trigger's Ready status to reflect the status of its associated importer: if the importer is unready, the trigger is also unready. This at least allows the user to track down which object is having problems by looking at the object they're aware of (the trigger).
Persona:
User
Exit Criteria
A Trigger can be Ready=False due to the Ready status of an associated importer.
Time Estimate (optional):
Additional context (optional)
Ideally the solution could be applied to the general problem of any KResource (an object exposing a Ready condition) dynamically depending on the status of any other KResource. Clients could then encode their own dependency graphs based on their specific use case.
/cc @n3wscott since we've discussed this in the past.
Problem
#1381 asks for a way to hide the complexity of creating importers from trigger creators for the simplest scenarios. One downside is that the ready status of hidden objects is also hidden: if an importer created on behalf of a user's trigger creation request fails to become ready, the user isn't able to easily determine that the importer is unready.
One way to solve this is to allow the trigger's Ready status to reflect the status of its associated importer: if the importer is unready, the trigger is also unready. This at least allows the user to track down which object is having problems by looking at the object they're aware of (the trigger).
Persona:
User
Exit Criteria
A Trigger can be Ready=False due to the Ready status of an associated importer.
Time Estimate (optional):
Additional context (optional)
Ideally the solution could be applied to the general problem of any KResource (an object exposing a Ready condition) dynamically depending on the status of any other KResource. Clients could then encode their own dependency graphs based on their specific use case.
/cc @n3wscott since we've discussed this in the past.