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

SIGSEGV on generating resources with a spec without x-kuadrant extensions #65

Merged
merged 1 commit into from
Apr 29, 2024

Conversation

jasonmadigan
Copy link
Member

@jasonmadigan jasonmadigan commented Apr 29, 2024

Quick fix to resolve a small bug:

#64

We could make this more complex by detecting the many permutations of inclusion of x-kuadrant extensions in specs, to warn/panic if none are found. That may be a better fix longer term (could be addressed this way as a follow-on PR if needs be - this gets us out of a hole right now).

Verifying

# With kuadrantctl 0.2.0
kuadrantctl generate kuadrant authpolicy --oas ./examples/oas3/petstore.yaml

=>

big old SIGSEGV

With this patch, no panic.

Have also patched HTTPRouteGatewayParentRefsFromOAS and HTTPRouteHostnamesFromOAS which have a similar bug.

@jasonmadigan
Copy link
Member Author

thanks @eguzki - patched up

@jasonmadigan jasonmadigan merged commit a211485 into main Apr 29, 2024
5 checks passed
@jasonmadigan jasonmadigan deleted the 64-sigsegv-fix branch April 29, 2024 13:54
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

Successfully merging this pull request may close these issues.

2 participants