Ivan

>as I would prefer to leave it for https://github.com/grafana/k6/pull/3217 which likely will completely redo the rest API either way. @mstoykov can you expand and define what it means for you...

>Both me and (AFAIK) Ned never intended for keepign this API Me neither, my focus was on not doing it as part of distributed execution. If we keep them independent...

We can close this issue, as expanding the current API is not in our plans, and as we plan to address #3217 which makes mostly useless `--linger` so, in the...

In https://github.com/grafana/k6/issues/3583 discussion, we set the hypothesis that k6 doesn't need a _real_ HTTP API v2 after we have implemented native distributed execution. Most of the current endpoints cover use...

Hi @lucasoares, I interpret this request for integrating the extension or natively support the Push Gateway in the k6's core. At the moment, based on the demand this is outside...

@na-- I pushed the changes for moving the access from fields to getter methods. Something like the following pseudo-code should work to avoid the type conversion all the time. Considering...

Closing, as this is not happening at the moment and requires a new iteration. We will come up with a new re-iterated proposal.

https://github.com/grafana/k6/blob/master/docs/design/019-file-api.md#possible-future-improvements

Hi @szuecs, I can imagine some use cases, but as @kullanici0606 it would be helpful to get a better explanation about your specifics. It would be nice to know what...

Hi @mohitk05 @szuecs, we met today with the team to discuss this issue. In summary, our position remains similar [as previously communicated](https://github.com/grafana/k6/issues/2054#issuecomment-1486646732): we might add support for this use-case as...