You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was a question in today's community call as to whether local-deploy is confusing. I was trying out local-deploy with DevContainers CLI on GitHub. I understand local as local machine, so when I run bicep inside GitHub Actions the local part is not really true. The 2nd part is deploy, but even in the documentation https://github.com/Azure/bicep/blob/main/docs/experimental/local-deploy.md the local extension is not even deploying anything. It is just running PS or bash script. So, deploy does not really mean that something has to be deployed.
Since Provider was renamed to Extension, why not bicep extension run [bicepparam], or bicep run if there are no subcommands under bicep extension?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
There was a question in today's community call as to whether local-deploy is confusing. I was trying out local-deploy with DevContainers CLI on GitHub. I understand local as local machine, so when I run bicep inside GitHub Actions the local part is not really true. The 2nd part is deploy, but even in the documentation https://github.com/Azure/bicep/blob/main/docs/experimental/local-deploy.md the local extension is not even deploying anything. It is just running PS or bash script. So, deploy does not really mean that something has to be deployed.
Since Provider was renamed to Extension, why not
bicep extension run [bicepparam]
, orbicep run
if there are no subcommands under bicep extension?Beta Was this translation helpful? Give feedback.
All reactions