Skip to content
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

Open
artursouza opened this issue Jul 23, 2020 · 2 comments
Open

Support STDIN input #91

artursouza opened this issue Jul 23, 2020 · 2 comments
Labels
question Further information is requested

Comments

@artursouza
Copy link
Contributor

Add support for STDIN input like:

echo "..." | bicep build - or echo "..." | bicep build

@alex-frankel
Copy link
Collaborator

@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 alex-frankel added the question Further information is requested label Sep 16, 2020
@artursouza
Copy link
Contributor Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants