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
CI Failure (key symptom) in RpkPluginTest.test_managed_byoc
#18334
Comments
Assuming this is infra issue. If not please reassign to Core, @jackietung-redpanda (cc: @michael-redpanda ) |
This is a real issue for This reveals that, in general, plugins (which could be any old executable provided by the user) probably should not load he shared libs that we ship as part of Or we completely shutoff the plugin capabilities for Notes:
|
Echoing comment from Slack -- I think we can gate plugin stuff on a build tag. This will require a separate root.go file in the rpk source tree; currently the file that installs all commands also has a huge chunk dedicated to plugin discovery. |
Wonder if we have a path forward here to close this out, @jackietung-redpanda ? |
Yes we do. The plan is to block conditionally compile out plugins path for FIPS. However this work is considered non-blocking for the FIPS projects and will be prioritized accordingly. In the meantime, I plan to merge this #18577 to clean up test reports. I think that will be sufficient to close out this issue. |
https://buildkite.com/redpanda/vtools/builds/13607
JIRA Link: CORE-2849
The text was updated successfully, but these errors were encountered: