* Add indexer crate and files
* POC searcher
incomplete schema
only indexes at startup
* POC search component frontend
* Demo of the frontend element
* add Results and Args as text
* minimal functionality
* Make jump to scripts by name
also flows and apps
* Add button on sidebar to open search
* Update lock on indexer after merge
* Make arrow key navigation compatible with scrol
* Show empty result screen and log as a coming feat
* Add summary to script searchable items
* Catch `parts is undefined` error (uFuzzy)
* Index refreshing using tokio interval
* Fix JobLoader workspace being wrongly defined
* Fix click outside
* Add debouncing for completed run search
* Binary mode working + job index tracker
* Warning for no license + fix height scrollbars on content search
* Make it compile without EE files
* remove panic to use errors
* Move global search
* Cleanup UI, no more tab switcher but clear placeholders and actions
* Add tantivy feature flag for windmill-api
* Rework indexer mode
* Mac compatibility for shortcut
* Update test for new run_server
* Prepare sqlx
* Mac compatibility
* Fix openapi yaml
* Fix frontend
* Frontend api fix
* Update docker-compose.yml and caddyfile
With the (by default deactivated) container and reverse proxy to use the
windmill indexer
* fix feature flag for tests
* fix feature falg for running tests
* fix feature flag for running tests
* Make content search use search modal instead
* Add tantivy feature to ee build steps
* Remove old Content search
* change volume location for indexer
* Update dependencies
* Prepare sqlx
* Uncomment line on docker compose
* Add line between input and results
* Update ee repo ref
* Add concurrency_key table and field to payload
Add a new table custom_concurrency_key for storing concurrency keys on a
per job basis. Add the field to the job payload to populate the table on
creation of a new job.
* Rename to custom_concurrency_key
Be more explicit about the nature of the option variable by calling it
a more appropriate name.
* Delete concurrency_keys on delete_expire_items
* Propagate db errors up
* Add ref to EE changes
* update sqlx
* Add concurrency_key to tests
* Revert renaming of FlowValue field
FlowValue field concurrency_key must be named concurrency_key for
serialization purposes.
* Remove debug print statement
* Get concurrency_key from Job
Whether it is a Completed job or a queued one, add a ways to get the
associated concurrency key
* Add endpoint to get concurrency_key
* Add endpoint and button to get job concurrency_key
Add a line with a link on the FlowMetadata that goes to the
concurrency_groups page. add endpoint to get the concurrency_key of a
job
* Merge concurrency_key tables into one
migration + change all related querrys
* Add concurrency plot to the runs page
* Prepare sqlx
* Add concurrency Key filter on UI
* Prepare sqlx
* Prepare sqlx
* Fix filter and order query
The limit makes more sense if we cut the older rows, so order by
started_at
* Factor interpolation to reuse on concurrency key
Factor the arg interpolation logic into a function and finish the
processing of concurrency key before insertion
* Remove old concurrency key processing logic
* Second transaction with userdb
To send all concurrency intervals but revealing only uuids of accessible
jobs, make a second transaction with the userdb.
* Remove old second endpoint
the intervals endpoint now also gets the concurrencyt key information
for all jobs
* Show external jobs
* Put filters into a dropdown
Create a ToggleButtonMore and put elements into a dropdown
* Add toggle between two graphs
* Add filter functionality to concurrency graph
* Improve concurrency graph front
* Fix concurrency groups page
* Prepare sqlx
* Add ref to ee
* Change migration to create new table instead
Instead of renaming the custom_concurrency_key_ended atble, we create a
new table and we will delete custom_concurrency_key_ended in the future
when it is no longer linked to any jobs
* Do small UI improvements
* Fix range fusion by not filtering past jobs
Instead of filtering jobs in the backend on a startedAfter value, limit
the query to 1000 and query all possible towards the past to get a good
context for the graph in most sane situations
* Improve frontend UI
