Open tim-chaffin opened 5 months ago
@tim-chaffin thanks for raising this issue. I think there is one thing to explain here:
backend
=== used for configuration and metadata persistence (this is used to provide all search-capabilities, data persistence,...)storage
=== actual storage kind to use for artifact storageIt is not possible to use local storage for backend
. Valid options are one of elasticsearch,dynamodb,cosmosdb
.
CosmosDB uses SQL-dialect.
Thanks for the hint, i think this should be part of the docs.
In your case set configuration.backend.type = cosmosdb
and also bear in mind to set configuration.backend.cosmosDB.endpoint
and configuration.backend.cosmosDB.masterKey
Thank you for helping, and clarifying these points. This helps significantly.
I'd be happy to help write this up? If you have a branch you'd like me to contribute to? Or I can fork and PR?
Additionally where would you like all of this documented specifically?
You are welcome :) Help would be really appreciated. For now the docs are still in the main repo
If you would contribute best way to achieve that is to fork and create a PR against the upstream.
PR for review: https://github.com/PacoVK/tapir/pull/396
What we're trying to do, is spin up Tapir in an Azure Kubernetes Service, with local configurations for the backend. We're using the Helm chart deployment, with the full config value is below.
What we've tried:
backend:
configuration, we've settype:
equal to "". It is my understanding that we should be able to deploy tapir, using local storage only.storage:
configuration tolocal
. However, the odd AWS region error still presents itself.Note: Ignore the IdP error for now. We'll be adding that in later. Trying to sort out the AWS related issue right now.
Full config.yml
Error encountered: