-
Notifications
You must be signed in to change notification settings - Fork 774
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
Running bicep build should compile everything in the directory #246
Comments
If we want to be able to create reusable modules this functionality is vital. This also will help with keeping bicep files more readable and manageable, some deployments are going to be quite large. A common pattern I have seen with customers using Terraform is that they will name the Terraform files for the functionality/resources it is deploying (ex. frontend.tf, backend.tf) and running their deployments from the root of the folder structure. |
This answer #1285 (comment) seems relevant. |
This has 8 or so upvotes across two different issues. Bicep build is also the highest used bicep cli commands after "bicep upgrad". While there are great options mentioned, users would have to ultimately search and find these issues each time to know the powershell commands. At first I was a big fan of changing the behavior of The reason for the --all flag is, what if a user mistakenly writes We could possibly put some safeguards to make sure this sort of mistake doesn't happen. I'm open to suggestions. As @StefanIvemo mentioned in #1285, it would be a great idea to have:
I propose this is retriaged. |
See #1285 for commands you can use to accomplish this today. |
It is nice to be able run bicep build from within a folder and if no file (s) provided as an argument the tools iterate through the folder and compiles all bicep files within that folder (I'm not sure we have a file that is equivalent to csproj for example in C#)
The text was updated successfully, but these errors were encountered: