cosmosdb mongodb collection update cannot set default TTL to -1

Describe the bug

When attempting to enable TTL on cosmosdb mongo collection with no default, TTL is disabled instead.

To Reproduce:

Run the following command on an existing cosmosdb mongodb collection:

az cosmosdb mongodb collection update --account-name {} --resource-group {} --database-name {} --name {} --idx "[{\"key\": {\"keys\": [\"_ts\"]},\"options\": {\"expireAfterSeconds\": -1}}]"

When inspecting the result in mongo shell, the result looks like this:

        {
                "v" : 1,
                "key" : {
                        "_ts" : 1
                },
                "name" : "_ts_1",
                "ns" : "db.collection"
        }

Expected Behavior

The command should set default TTL to -1

        {
                "expireAfterSeconds" : -1,
                "v" : 1,
                "key" : {
                        "_ts" : 1
                },
                "name" : "_ts_1",
                "ns" : "db.collection"
        }

Environment Summary

Windows-10-10.0.17763-SP0
Python 3.6.6
Installer: MSI

azure-cli 2.5.0

Additional Context

Note that setting default TTL to -1 works fine if I use the deprecated command az cosmosdb collection update --name {} --resource-group-name {} --db-name {} --collection-name {} --default-ttl -1

[shurd]

Hi @nohajc, I am looking into this issue. I will update once I finish my investigation

[MehaKaushik]

Since we do not have a timeline for this ask in the near future and we tracking it internally, I am closing this issue from github.