list pipeline api endpoint should be more elaborate

[TimoKramer]

I am thinking about a solution for a more elaborate query of the pipeline endpoint. I think group and name could be left like it is but then I would prefer to have them work on their own, too. Like this

./wendy --name test | jq .
[
  {
    "name": "dev:test",
    "data": {
...
  }
]

that would need a sql query that works based on a regex like this maybe:

SELECT p.name, p.image
FROM "pipelines" p
WHERE p.name LIKE '%:test'

The other option would be to offer entering the name of the pipeline as a whole. Offering name and group on their own but expecting both is confusing. Maybe like this:

./wendy --name dev:test | jq .
[
  {
    "name": "dev:test",
    "data": {
...
  }
]

And another thing: I don't get the status option. That should be worked out because it seems not to be implemented yet. Or completely taken out.

[lispyclouds]

Not implemented as in if you mean it looks commented like this:

-- :name get-pipelines :query :many
SELECT p.name, p.image
FROM "pipelines" p
WHERE 1 = 1
--~ (when (not-empty (:pipeline params)) "AND p.name = :pipeline")
/*~ (when (not-empty (:status params)) "
      AND EXISTS (SELECT r.status
		FROM runs r
		WHERE r.pipeline = p.name
 		      AND :status = r.status
		LIMIT 1)")
~*/

it is part of the HugSQL syntax
Was that the question you had?

[lispyclouds]

maybe we can make the filtering explicit. with --name --group etc.

[TimoKramer]

Right, it looked linke commented;)

…

On 1 April 2020 21:27:35 CEST, "Rahuλ Dé" ***@***.***> wrote: Not implemented as in if you mean it looks commented like this: ```sql -- :name get-pipelines :query :many SELECT p.name, p.image FROM "pipelines" p WHERE 1 = 1 --~ (when (not-empty (:pipeline params)) "AND p.name = :pipeline") /*~ (when (not-empty (:status params)) " AND EXISTS (SELECT r.status FROM runs r WHERE r.pipeline = p.name AND :status = r.status LIMIT 1)") ~*/ ``` it is part of the HugSQL [syntax](https://www.hugsql.org/#using-expressions) Was that the question you had? -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #75 (comment)

[TimoKramer]

Closing because it works now.