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

Feature Request: Include stdout and stderr for each step #23

Open
Zxilly opened this issue Aug 24, 2024 · 4 comments
Open

Feature Request: Include stdout and stderr for each step #23

Zxilly opened this issue Aug 24, 2024 · 4 comments

Comments

@Zxilly
Copy link

Zxilly commented Aug 24, 2024

I'm using codapi as a compiled language backend. It should compile the source first then run the binary. During these actions, I want to get the warning compiler print and the stderr from the compiled binary, which is impossible with the current api design.

@gedw99
Copy link

gedw99 commented Aug 29, 2024

I was going to suggest exactly this too .

@nalgeon
Copy link
Owner

nalgeon commented Nov 9, 2024

Not currently planned, see #24 for details:

To be honest, I prefer the current behavior, and I'd rather not add a config switch.
I don't currently see enough compelling reasons to complicate this behavior.

@gengle
Copy link

gengle commented Dec 22, 2024

Having the build output visible could introduce security risks. You may want to consider doing intake validation using Open Policy Agent or similar. Rego language is written in go, but Microsoft has a Rust port that's incredible fast.

https://github.com/microsoft/regorus

@Zxilly
Copy link
Author

Zxilly commented Dec 22, 2024

@gengle Everything happens in the container. I don't think it poses any additional risk.
In fact, the current design would get the same output, you'd just have a hard time separating those outputs.

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

No branches or pull requests

4 participants