* feat(CLI): add a new update from flow source CLI
* feat(CLI): use the repository instead of the webserver
* feat(CLI): change command name to SyncFromSource
---------
Co-authored-by: nKwiatkowski <nkwiatkowski@kestra.io>
If a test mis-behave, for ex starting an execution but not terminating it, as the default termination grace period is 5mn it can take very long time to wait for post-test terminaison.
Switching to a termination grace period of 5s may help.
I also detect that the ExecutionControllerRunner test when launching the test suite, would not properly kill the `sleep-long` flow so waiting for it to complete, or the termination grace period. When a test that use this flow is launched separatly it works properly. As a safety net I reduce the sleep from 5mn to 30s.
* Fix/sdk changes (#12411)
* fix: kv controller remove namespace check
* clean(API): add query to filter parameter
* fix: flow update not deprecated
* clean(API): add deprecated on open api
* feat: executions annotations for skipping, follow method generation in sdk
* feat: add typing indication to validateTask
* fix(flowController): set correct hidden for json method in
* fix: optional params in delete executions endpoints
* fix: inputs/outputs as object
* change KV schema type to be object
* add back , deprecated = false on flow update, otherwise its marked as deprecated
* Revert "add back , deprecated = false on flow update, otherwise its marked as deprecated"
This reverts commit 3772404b68f14f0a80af9e0adb9952d58e9102b4.
* feat(API): add multipart to openAPI
* feat(API): add multipart to openAPI
* fix: only use plain-text for setKeyValue endpoint
* fix: KV command test
* chore: add multipart vendor annotations for custom generation on SDK
---------
Co-authored-by: YannC. <ycoornaert@kestra.io>
Co-authored-by: nKwiatkowski <nkwiatkowski@kestra.io>
* fix: kv test remove content type
---------
Co-authored-by: Roman Acevedo <roman.acevedo62@gmail.com>
Co-authored-by: nKwiatkowski <nkwiatkowski@kestra.io>
A counter allow to lock by flow which solves the race when two executions are created at the same time and the executoion_runnings table is empty.
Evaluating concurrency limit on the main executionQueue method also avoid an unexpected behavior where the CREATED execution is processed twice as its status didn't change immediatly when QUEUED.
Closes https://github.com/kestra-io/kestra-ee/issues/4877
* fix(core): Add warning logs for mismatched (Parent-Subflow) inputs for subflow plugin.
* feat(tests): add test coverage for cli commands with no repository configurations
* refactor(tests): enhance test assertions and namings
* refactor(tests): replace HelloCommand with Namespace KV helper in no-config tests
- Use Namespace KV command (with no params) to verify repo-independent CLI behavior
- Remove HelloCommand usage in NoConfigCommandTest
- Keep FlowCreateCommand case to assert repo-dependent commands fail without config
* fix(tests): add sleep before restarting to make sure the queue is clean
* fix(tests): add retry on a flaky test
---------
Co-authored-by: nKwiatkowski <nkwiatkowski@kestra.io>
* fix(test): disable flaky test and add configuration to the ELS indexer poll duration
* fix(test): retry a flaky test and fix a flaky
* feat(test): disable a test until we have time to fix the bug
---------
Co-authored-by: nKwiatkowski <nkwiatkowski@kestra.io>
This will log this kind of line at startup, helping to understand possible infrastructure limitation by looking at the starting logs.
```
14:38:17.018 INFO main i.k.c.c.s.AbstractServerCommand Machine information: 16 available cpu(s), 2048MB max memory, Java version 21.0.5+11-LTS
```
* test: parallelize AbstractRunnerTest
* test: add TestsUtils.randomTenant(..) function
* test: i think i found a bug
* revert debug
* test: add comment on potential bug, make test pass
* test: fix test metadata
* test: unflaky PluginDefaultServiceTest by separating class
* test: add log on JdbcServiceLivenessCoordinatorTest to debug
* test: cleanup debug log
* fix
