-
Notifications
You must be signed in to change notification settings - Fork 33
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
[Feature Request]: ARM (Azure) template deployment #71
Comments
|
Discussion with Azure folks: We are creating a Solution Template since we are not interested in charging. It's a give away without retaining any rights as the publisher. Refer to this example: https://github.com/Azure/Commercial-Marketplace-SaaS-Accelerator-Offer
Once you have ARM templates ready, use ARM TTK (toolkit) to validate And then publish and test in your own subscription using a Service Catalog: |
@wi0lono Is the issue good to close? Please provide status |
@DevvStrange, any update here? |
Hi @wi0lono, as discussed could you please add the latest updates here and the scope of improvement required as in to take this further. |
Waiting for Atarv from Microsoft for inputs |
Hi, sorry for the late update! What remains incomplete is
Please let me know if you have any other questions. |
@DevvStrange, Hi Arun, would you be working on the incomplete items mentioned by Atharv? |
Yes Lekha, I will take this up further. |
@DevvStrange any update on this? |
Is your feature request related to a problem? Please describe.
We need an ARM template-based deployment that works as easily as the following:
Describe the solution you'd like
We can leverage the public images for the containers. e.g.
opennyaiin/jugalbandi-manager:api-latest
We need to run an SQL script for DB upgrade / initialization.
We assume Azure OpenAI is configured before and we have the relevant keys. Similarly Bhashini keys are inputed
Refer to this ChatGPT conversation: https://chatgpt.com/share/c960b010-2ad8-48f4-b0df-5301c78922a9
Later:
We need to use AKS (kubernetes) for deployment
We need to use Managed Identity (as per latest guidelines) instead of using Storage Account / EventHubs keys
Additional context
No response
The text was updated successfully, but these errors were encountered: