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

[Issue] next-steps.md states incorrect manifests directory #4401

Open
1 task done
michaelmcneilnet opened this issue Oct 3, 2024 · 3 comments
Open
1 task done

[Issue] next-steps.md states incorrect manifests directory #4401

michaelmcneilnet opened this issue Oct 3, 2024 · 3 comments
Assignees
Labels
aspire bug Something isn't working customer-reported identify a customer issue documentation Improvements or additions to documentation question
Milestone

Comments

@michaelmcneilnet
Copy link

Output from azd version
azd version 1.10.1 (commit 31409a33266fb4a5fdbb644bc83988e725d6c7c9)

Describe the bug
The generated next-steps.md file states

In addition, for each project resource referenced by your app host, a containerApp.tmpl.yaml file will be created in a directory named manifests next the project file. This file contains the infrastructure as code for running the project on Azure Container Apps.

This isn't the case for me. These tpml.yaml files are within the infra/ folder along with the rest of the generated bicep , after running azd infra synth. I am using Aspire with packages at 9.0.0-preview.4.24502.4

To Reproduce

  1. Run azd init
  2. Run azd infra synth
  3. View the next-steps.md file.

Expected behavior
The next-steps.md file states that the containerApp.tmpl.yaml files are within the infra/ folder.

@michaelmcneilnet michaelmcneilnet changed the title [Issue] - next-steps.md states incorrect manifests directory [Issue] next-steps.md states incorrect manifests directory Oct 3, 2024
@rajeshkamal5050 rajeshkamal5050 added bug Something isn't working documentation Improvements or additions to documentation aspire labels Oct 3, 2024
@rajeshkamal5050 rajeshkamal5050 added this to the Oct 2024 milestone Oct 3, 2024
@rajeshkamal5050
Copy link
Contributor

@weikanglim can we fix the generated next-steps doc?

@michaelmcneilnet
Copy link
Author

@weikanglim
Copy link
Contributor

We'll get the docs updated to reflect the newly introduced product behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aspire bug Something isn't working customer-reported identify a customer issue documentation Improvements or additions to documentation question
Projects
None yet
Development

No branches or pull requests

4 participants