-
-
Notifications
You must be signed in to change notification settings - Fork 402
feat: add test overrides for nginx #3369
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
Conversation
4175399
to
afee93b
Compare
Thanks @theseion. Can we help you get this PR over the line? What is still missing here? |
Some finishing touches to go-ftw are needed. Need to pick up work on that again. Probably over Christmas. |
That's a reasonable time frame. Thanks for the info. Do we need this for v4, or can the label be removed? |
I think we can ship 4.0 without this. |
Thank you |
@theseion Is this still blocked by missing go-ftw features? I'd like to add the status of the nginx regression testing endeavour to the March agenda. |
Yes, I need to implement some things in go-ftw to support multiple engines, the status engine, etc. |
afee93b
to
3c3c5e8
Compare
3c3c5e8
to
c2eef52
Compare
Keeping my fingers crossed here ... :) |
c2eef52
to
f877cc6
Compare
5f344d0
to
85b5606
Compare
9e78ce7
to
246116b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AWESOME! Hopefully we can iterate quickly on this one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AWESOME! Hopefully we can iterate quickly on this one.
2361f94
to
c8d3f52
Compare
@fzipi rebased. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@theseion So, after the correctness checks, what is your plan here?
I mean, from what I see there is no actual nginx test being run here, right? (e.g. matrix doesn't run for modsec3-nginx
)
Are we first pushing this change, then adding it to the matrix? Maybe we want also to rename the matrix variable to platform
instead of modsec_version
....
I wanted to create a separate PR for both of those. Once we've merged, I'll also open a PR for submitting the JSON schemas to I haven't yet had a good idea on how to make people aware of the mapping between go-ftw and ftw-tests-schema. I thought about adding a schema version to the spec but that feels a bit clunky. Maybe we should couple the versioning of schema and go-ftw. Not a fan of t F438 hat either though... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Somehow I can't see these last two. But they can be forgotten, as they are URL changes.
They were hidden (happens when there are too many conversations). |
No description provided.