Jose Esparza

@deyandyankov, could an authorization parameter be considered in the future? This can be an usability upgrade.

@deyandyankov I bundled a `MLFlow` object inside a general `MLFlowInstance` type that allows us to save the most important project configurations: `base_uri`, `experiment_name` and `artifact_location` (we can expand them, it's...

Hello @math4mad. Thanks for your appreciation. Our Logger implementation must work with the DagsHub MLFlow instance, because we are using its API endpoints. However, I'm not pretty sure if the...

Hello, I think the issue comes from the different forms of uploading to a `mlflow` instance. There is no dedicated REST endpoint to upload a run artifact (and that's awful)....

@ablaom do you think is a good idea to replicate the environment variable approach implemented in MLJFlow testing suite? I think it can ensure the user to run all the...

To improve the project testability, I suggest to use [BrokenRecord.jl](https://github.com/JuliaTesting/BrokenRecord.jl). It brings us a "cassette" approach to record the HTTP requests, removing the necessity of having a `mlflow` instance running...

I don't know if there's other than DagsHub. I consider the API base URL approach as a good one. With that, we don't need to be aware of if it's...

Hello @math4mad. That's not the way to authenticate into an `mlflow` instance. To achieve this, we need to have our base64-encoded credentials and pass it through the authorization header. ```julia...

This last change is using the generic `/ajax-api` prefix on each endpoint to allow compatibility with different platforms. **Notes:** - Original MLFlow instances use base64 to encode authorization headers (based...

@deyandyankov Could it be related with the way `mlflow` handles this pseudo-random names? Maybe they use the unix timestamp.