Support for analytical store in azurerm_cosmosdb_sql_container

[TobiTh]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Could you please add the possibility to enable the analytical store when creating a new sql container?
In Azure, you can enable it in the "create container" dialog:

New or Affected Resource(s)

• azurerm_XXXXX

Potential Terraform Configuration

resource "azurerm_cosmosdb_sql_container" "example" {
  name                  = "example-container"
  resource_group_name   = azurerm_cosmosdb_account.example.resource_group_name
  account_name          = azurerm_cosmosdb_account.example.name
  database_name         = azurerm_cosmosdb_sql_database.example.name
  partition_key_path    = "/definition/id"
  partition_key_version = 1
  throughput            = 400
  enable_analytical_store = true #new

  indexing_policy {
    indexing_mode = "Consistent"

    included_path {
      path = "/*"
    }

    included_path {
      path = "/included/?"
    }

    excluded_path {
      path = "/excluded/?"
    }
  }

  unique_key {
    paths = ["/definition/idlong", "/definition/idshort"]
  }
}

References

The following pull request fixes the enabling of the analytical storage for a cosmosdb account (not a sql container)
#10055

[favoretti]

This one has been implemented and merged as part of #10055

[TobiTh]

@favoretti Yes, this enables the capability of analytical storage in the cosmosdb account. But we still need to enable the analytical store for each cosmosdb sql container seperately.

[favoretti]

Ahh, sorry, lacked coffee...

…

On Tue, 19 Jan 2021 at 13:05, TobiTh ***@***.***> wrote: @favoretti <https://github.com/favoretti> Yes, this enables the capability of analytical storage in the cosmosdb account. But we still need to enable the analytical store for each cosmosdb sql container seperately. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10198 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGERNWFCHIZO4N5IPBICI3S2VYPHANCNFSM4WD5DSEQ> .

[T1loc]

This one has been implemented and merged as part of #10055

That's what I meant by the PR I didn't open.
The option shown by @TobiTh can only be define at container creation time.

There is also this parameter to take into account:

[bm77525-kr]

It looks like the capability for this should be there in the current SDK if I'm reading it right. The other SDK's seem to enable this on containers by setting the analyticalStorageTtl property at creation. From the looks of the latest azurerm provider, it's using the 2020-04-01 API which supports that property. Does this just need to be exposed in the provider?

[FlipABit]

@favoretti Sounds like this is potentially supported via the SDK that's currently in use now, yes?

[favoretti]

Yep, I'm happy to implement it, just trying to understand how the portal shows off/on (no default)/on as a choice and API has an integer as a value..

[favoretti]

Nevemind, tests showed how it works, which is sort of weird, but let me try an implementation.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.