NG: UX - Service/Pipeline: it asks for artifact input even if artifact is not required in pipeline
long-term
C
Chocolate Tahr
Hi,
In CG, if a pipeline was not using the artifact tag, it was not asking for the artifact.
However, in NG, regardless of usage, if the field is marked as input in the service and the service is selected, then it asks for artifact every time.
Its not ideal and it adds the confusion on why its asking for artifact in the rotate pods pipeline or delete service or any other such kind of pipeline.
Log In
Rohan Gupta
long-term
Adding this to our backlog, agreed it shouldn't ask for the tag in this scenario. We can enhance the default behavior.