Skip to content
This repository has been archived by the owner on Sep 18, 2024. It is now read-only.

Suggestions #5

Open
markjbrown opened this issue Aug 27, 2024 · 2 comments
Open

Suggestions #5

markjbrown opened this issue Aug 27, 2024 · 2 comments

Comments

@markjbrown
Copy link
Contributor

You can simplify the deployment experience for the user and save a couple of steps the user needs to complete manually.

  1. Deploy the code into the azure function directly from bicep instead of manually deploying in step 5.
  2. Tracing can also be setup in the bicep eliminating step 6.
@Pilchie
Copy link
Contributor

Pilchie commented Aug 28, 2024

@amisi01 tried to deploy the azure function from bicep, but couldn't get it to work. Any pointers to how to get this to work?

@markjbrown
Copy link
Contributor Author

You have to use azd to make that work. This github repo shows how to do it. https://github.com/Azure-Samples/functions-quickstart-dotnet-azd and includes nearly everything you need. You will need to add the non-function specific stuff but includes functions, identity, storage. Plus stuff you probably dont need: vnet, private endpoints, etc.

Also, make sure to copy azure.yaml into the root of the project.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants