Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow multiple capabilities in CosmosDB Account #42

Closed
jdocampo opened this issue Jan 2, 2023 · 0 comments · Fixed by #43
Closed

Allow multiple capabilities in CosmosDB Account #42

jdocampo opened this issue Jan 2, 2023 · 0 comments · Fixed by #43
Assignees
Labels
bug Something isn't working module: enhancement New feature or request

Comments

@jdocampo
Copy link
Member

jdocampo commented Jan 2, 2023

Right now only one value for enable_capabilities is allowed, and if leave default to empty, it gives an error:
Error: expected capabilities.0.name to be one of [EnableAggregationPipeline EnableCassandra EnableGremlin EnableTable EnableServerless EnableMongo MongoDBv3.4 mongoEnableDocLevelTTL DisableRateLimitingResponses AllowSelfServeUpgradeToMongo36], got

The parameter should change to enable_capabilities and be a list of strings, defaulting to an empty list

jdocampo added a commit that referenced this issue Jan 2, 2023
@jdocampo jdocampo self-assigned this Jan 2, 2023
@jdocampo jdocampo added bug Something isn't working module: enhancement New feature or request labels Jan 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working module: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant