Skip to content

Debug publish mode #9019

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.

Sign up for GitHub

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

Jump to bottom
Open
1 task done
RamType0 opened this issue Apr 29, 2025 · 3 comments
Open
1 task done

Debug publish mode #9019

RamType0 opened this issue Apr 29, 2025 · 3 comments
Labels
area-deployment

Comments

@RamType0
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

We often met weird error while generating bicep manifest with Aspire. (e.g. unsupported resource type: project.v1)
But we could not debug it.

Describe the solution you'd like

Add feature to debug publish mode,

Additional context

No response
@github-actions github-actions bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Apr 29, 2025
@davidfowl davidfowl added area-deployment and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Apr 29, 2025
@davidfowl
Copy link
Member

I assume you mean azd right?

@vhvb1989 ?

@RamType0
Copy link
Author

Ideally, I want unified framework for any kind of publish(e.g, Azure, AWS)
But it is OK even if it is only for Azure.

@davidfowl
Copy link
Member

I'm not sure what you mean. Can you clarify?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-deployment
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@davidfowl @RamType0