Skip to content

Help deploying to Azure Container Apps environment #45

Description

@l3ender

Hello! We are deploying this app for the first time and are greatly looking forward to its capabilities.

We want to deploy it to Azure and so we are following the steps on Deploy in Azure Container Apps. However, we are not very familiar with the Azure Developer CLI and so we are facing a bit of trouble and have a few questions.

  1. We assume that cloning this repo is required and that azd up command should be run within the repo, is that correct? We want to confirm because it isn't mentioned in the doc.
  2. We have configured azd env values in our local as mentioned in the readme:
    azd env set AZURE_CLIENT_ID "..."
    azd env set AZURE_ENV_NAME "copilot-usage-advanced-dashboard"
    # ...
    azd env set GH_ORGANIZATION_SLUGS "org1,org2"
    azd env set-secret GH_PAT
    We confirmed the values:
    -> azd env get-values -e copilot-usage-advanced-dashboard
    AZURE_CLIENT_ID="..."
    # ...
    GH_ORGANIZATION_SLUGS="org1,org2"
    GH_PAT="akvs://..."
    However, even after doing that, we see the following being prompted when running the deploy command:
    -> azd up
    ? Enter a value for the 'githubOrganizationSlugs' infrastructure parameter:
    Our assumption is that these values would get retrieved from the environment we had configured, but it looks like they need to be manually added. When we readd the value for org slugs and hit enter, we are then prompted the same for githubPat:
    ? Enter a value for the 'githubPat' infrastructure secured parameter:
    Can you please advise if this is expected and if we should re-enter all the values from the environment? If so, does the environment config serve a different purpose? For the githubPat value, do we enter the raw value or the reference to the key vault entry (e.g. akvs://{subscription-id}/{key-vault-name}/{secret-name})?
  3. Once the resources are deployed and the app is working, are any of the local Azure Developer environment config needed or can the environment be managed (and/or updated) via other automation or even manual changes in the Azure portal?

In general, we want to deploy the resources into Azure and we appreciate the automation of that using azd, but are used to other processes by which resources are initially deployed and so aren't sure on some of the above.

Thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions