-
Notifications
You must be signed in to change notification settings - Fork 564
[Meta] Integration Validation Refactoring #3680
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
Comments
Is this really related DAC or should this target main? |
Good point! This should target main 👍 |
This might be a duplicate of (or should be added as |
We should make this measurable and time bound in the design of this (potentially even making this a meta itself).
IMO this is still very ambiguous, so we should design and decide on what do move forward on. |
Updated to make this a meta and have time bound constraints for implementation. |
Update 10/9/24Deprioritized in favor of Falco integration work PM request, moving to Q3. |
Related Issue
#3618
This is a decoupled issue from #3618 to reduce the complexity of the PR review and to more atomically test the changes. Additionally this captures the desire to refactor to make this process smoother while decoupling it from other approaches to solving BYOS.
Summary
We may need to refactor the integrations validation for increased performance and ease of maintenance. This issue is to track the 4 steps needed to address this concern.
Steps/tasks 1-2 should take approximately half a sprint to complete, with the LOE cutoff for proceeding being 1 full sprint of refactoring work.
The text was updated successfully, but these errors were encountered: