Retryable writes are not supported

[diegoleme]

Feature Request

I want to configure the retryWrites

Detailed Description

Today I get the following error: Retryable writes are not supported. And the parameter retryWrites=false solves this problem

[addaleax]

@diegoleme Can you share exact steps to reproduce? :slightly_smiling_face:

[diegoleme]

I can't actually configure retryWrites via the interface. And I can't use Connect with connection string because I need to insert a .pem certificate.

[addaleax]

@diegoleme I see – I’ve opened https://jira.mongodb.org/browse/VSCODE-301 to track this feature request on our side :+1:

That being said, I think you generally should also be able to use Connect with connection string. Can you connect using the regular connection method, copy the connection string, and then add &retryWrites=false manually, then connect with that?

Can you maybe also share what specifically brings up the Retryable writes are not supported, if you happen to know, so that we have more information about how to prioritize this?

[diegoleme]

That being said, I think you generally should also be able to use Connect with connection string. Can you connect using the regular connection method, copy the connection string, and then add &retryWrites=false manually, then connect with that?

And how do I make Connect with connection string configure ssl/tsl with a .pem file with CA?

[addaleax]

@diegoleme You can add &tlsCAFile=filename (although you may need to percent-escape the filename, just like other connection string parameters).

[diegoleme]

@addaleax I add &tlsCAFile=filename and percent-escape the filename.

Using mongosh I can connect via command line with this URL, but it gives an error using the Connect with connection string.

Can I debug somehow?

[addaleax]

@diegoleme What error are you getting in that case?

[diegoleme]

@addaleax The Failed to connect error appears on the output panel.

[alenakhineika]

Hey, @diegoleme could you please try the latest version of the extension and let us know if the issue is gone or remains?

[alenakhineika]

Closing the issue because of lack of activity. Feel free to reopen if the problem persists.