Skip to content

next-steps.md

Latest commit

 

History

History
64 lines (40 loc) · 3.41 KB

next-steps.md

File metadata and controls

64 lines (40 loc) · 3.41 KB

Next Steps after azd init

Table of Contents

  1. Next Steps
    1. Provision infrastructure
    2. Modify infrastructure
    3. Getting to production-ready
  2. Billing
  3. Troubleshooting

Next Steps

Provision infrastructure and deploy application code

Run azd up to provision your infrastructure and deploy to Azure in one step (or run azd provision then azd deploy to accomplish the tasks separately). Visit the service endpoints listed to see your application up-and-running!

To troubleshoot any issues, see troubleshooting.

Modify infrastructure

To describe the infrastructure and application, azure.yaml was added. This file contains all services and resources that describe your application.

To add new services or resources, run azd add. You may also edit the azure.yaml file directly if needed.

Getting to production-ready

When needed, azd generates the required infrastructure as code in memory and uses it. If you would like to see or modify the infrastructure that azd uses, run azd infra gen to persist it to disk.

If you do this, some additional directories will be created:

- infra/            # Infrastructure as Code (bicep) files
  - main.bicep      # main deployment module
  - resources.bicep # resources shared across your application's services
  - modules/        # Library modules

Note: Once you have generated your infrastructure to disk, those files are the source of truth for azd. Any changes made to azure.yaml (such as through azd add) will not be reflected in the infrastructure until you regenerate it with azd infra gen again. It will prompt you before overwriting files. You can pass --force to force azd infra gen to overwrite the files without prompting.

Finally, run azd pipeline config to configure a CI/CD deployment pipeline.

Billing

Visit the Cost Management + Billing page in Azure Portal to track current spend. For more information about how you're billed, and how you can monitor the costs incurred in your Azure subscriptions, visit billing overview.

Troubleshooting

Q: I visited the service endpoint listed, and I'm seeing a blank page, a generic welcome page, or an error page.

A: Your service may have failed to start, or it may be missing some configuration settings. To investigate further:

  1. Run azd show. Click on the link under "View in Azure Portal" to open the resource group in Azure Portal.
  2. Navigate to the specific Container App service that is failing to deploy.
  3. Click on the failing revision under "Revisions with Issues".
  4. Review "Status details" for more information about the type of failure.
  5. Observe the log outputs from Console log stream and System log stream to identify any errors.
  6. If logs are written to disk, use Console in the navigation to connect to a shell within the running container.

For more troubleshooting information, visit Container Apps troubleshooting.

Additional information

For additional information about setting up your azd project, visit our official docs.