Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Awesome AZD team. We are working with the App Service team, the App Service writers, and Cloud Advocacy to add FastAPI support to this article:
https://learn.microsoft.com/en-us/azure/app-service/tutorial-python-postgresql-app
... and one of those requirements is to add azd support (as a template). We basically copied the Flask version of the \infra and made almost no changes to that part. Please let me know if there's anything we can do to expedite this. Thank you!
Here's what you asked for:
Please fill out this template! There are three different types of contributions, feel free to delete the checklists that are not applicable to your contribution type.
If you are submitting a new
azd
template to the galleryFill this out if you want your template to be added to the awesome-azd gallery!
Your template repository
Place your template repository link here:
REVIEWERS PLEASE READ THIS
Looks like the instructions may have changed here so I did as much as I could. For example, I added an entry to
/website/src/static/templates.json
, and since this is the FastAPI version of an existing AZD template, I just used the same tags (changing 'Flask' to 'FastAPI').Added an entry to https://github.com/Azure/awesome-azd/blob/main/website/src/data/users.tsx that includes:
Template title - A short title that reflects the local application stack that someone could use to get their application on Azure (e.g. "Containerized React Web App with Java API and MongoDB")
Description - 1-2 sentence description of the architecture (e.g. Azure services) or solution that is defined by the template.
Architecture Diagram or Application Screenshot - The image should include all services and their connections (example). You should add the image to the
website/src/data/images/
.Link to Author's GitHub or other relevant website - Used for attribution
Author's Name - Name to credit on the gallery card
Link to template source - Link to the template GitHub repo
Tags - Specify tags to represent the template. If you don't see a relevant tag for your template? Feel free to add one!
Required tags:
"msft"
) or Community-authored ("community"
)"bicep"
or"terraform"
)"new"
tag for any newly authored templatesIn the PR comment, if you can also add a link to the PR where you made your repo
azd
compatible this will allow us to provide feedback on your template and speed up the review process.^^ Did not do this because we build the application starting with the Flask version of the repo (which already had the \infra\ bicep files) and didn't make any changes.
If you are submitting a resource to be added to the awesome-azd README: