Draft
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
rr404
force-pushed
the
jdv_usecase_blaas_to_firewall
branch
from
823a15a to
a31a3d0
Compare
added 13 commits
January 13, 2025 17:10
rr404
force-pushed
the
jdv_usecase_blaas_to_firewall
branch
from
b3897d2 to
d630d5c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Better adapt in new usecase section of trouble shootting or in guides
Inital idea was to add a usecase in there to judge the level of abstraction we should have in them:
Turns out that for this BL usecase I was not happy with the state of the blocklist section and start a few changes