Brian Flores

> Hi Maintainers , @ylwu-amzn Can you please review Hi Muneer, will bring up your PR on todays sprint. We appreciate your patience

Hi @10000-ki, thank you for posting this. Have you considered the alternative way to update the connector? You could automate this procedure if you really wanted to you just need...

Actually this is a better alternative instead of un-deploying you can do it like how it states here https://opensearch.org/docs/latest/ml-commons-plugin/remote-models/connectors/#updating-connector-credentials

Please ignore the below message we have an update: Hey @10000-ki, apologies for the late response. ~~I just tried updating a connector myself and it seems to work. I am...

Hey @10000-ki, thanks to @b4sjoo we reviewed internally and noticed that there is a bug when dealing with standalone connectors. For now you might have to undeploy and make the...

hi @10000-ki I can understand why this is a bad experience for you. Since the standalone connector makes you have to undeploy, update connector and deploy. I think for a...

> seeing VisualizationIT failing again but with different error. #3353 Hmm This is confusing I would think that the retry would help but like you said [here](https://github.com/opensearch-project/ml-commons/pull/3353#issuecomment-2580644676) it didnt help....

Hey @Hailong-am do you mind taking a look? Thanks

Hey Hailong, we are trying to get to paste the stack traces with reproduction line too. Thankfully this [build failure log](https://github.com/opensearch-project/ml-commons/actions/runs/12684342775/job/35381998022#step:7:3482) didn't expire. Can you take a look?

Adding the log here in txt format so it doesn't expire [6_Build and Test MLCommons Plugin on linux (21).txt](https://github.com/user-attachments/files/18578201/6_Build.and.Test.MLCommons.Plugin.on.linux.21.txt) Here is another [example](https://github.com/opensearch-project/ml-commons/actions/runs/12694930908/job/35385810345#step:7:3503) of another build failure. Linking the txt...