-
Notifications
You must be signed in to change notification settings - Fork 49
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
GenericContainer with type: airship skips empty lines in stdout #471
Comments
@aodinokov I know you put in a workaround for this but which switches back to a KRM format until the Airship format is handled correctly. With that in mind, what is the urgency on resolving this bug -- do you think it's required for Airship v2.0, or could it wait for a v2.1? |
@mattmceuen, In my opinion, it is not urgent. Airship containers still can be used, as designed to perform all actions, for example, kubectl commands, or image building, while KRM containers are used to process YAMLs. |
@mattmceuen I agree with @teoyaomiqui - KRM-based generic container is enough. Airship-generic container was the attempt to keep the same API, but extend features, e.g. be able to call container in privileged mode, that was necessary for image-builder. Since image-builder was integrated in another way, it's not urgent. |
I don't think it is a good first issue, the fix may not be lengthy, but the design of the solution requires a deep understanding of go, docker SDK, krm functions, and airshipctl itself. |
I completely agree with @teoyaomiqui. Based on what I saw in it won't be so easy. |
I can work on this, please assign to me. |
@joshuaherrera , I don't think it's relevant anymore, cc @raliev12 |
@aodinokov ok if this isn't relevant I will work on another issue. Thank you. |
@aodinokov do we want to go ahead & close this then? Thanks. |
Describe the bug
Before switching back to GenericContainer type:krm (see this patchset) execution of
during gate script run produced file
/tmp/airship/airshipctl/manifests/site/test-site/target/generator/results/generated/secrets.yaml
that contains:
The expected result should look like
Steps To Reproduce
Minimal steps to reproduce the issue:
Expected behavior
The generated file must contain empty string and decryption must work (script must not fail)
Environment
cc: @teoyaomiqui
The text was updated successfully, but these errors were encountered: