-
Notifications
You must be signed in to change notification settings - Fork 731
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
Support STDIN input #91
Comments
@artursouza - we are triaging all of our issues. Is supporting stdin still relevant? If so, can you provide an example for where this would be used. |
@alex-frankel This can be used for scenarios where user has a single file to be built and the output to be used in another command without creating a temporary file. If bicep deploys directly from a bicep file, then this issue is less relevant. In other words, accepting stdin input enables users to deploy their bicep files without creating a temporary file. |
Add support for STDIN input like:
echo "..." | bicep build -
orecho "..." | bicep build
The text was updated successfully, but these errors were encountered: