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
Make Firewalls assignable to multiple subnets #1456
Merged
Merged
Conversation
This file contains 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
furkansahin
force-pushed
the
fw_to_subnet
branch
from
April 17, 2024 08:52
5263f4d
to
faaecd4
Compare
furkansahin
force-pushed
the
multiple_fws_per_subn
branch
2 times, most recently
from
April 17, 2024 12:03
294708d
to
2f1a32c
Compare
fdr
reviewed
Apr 23, 2024
furkansahin
force-pushed
the
fw_to_subnet
branch
from
April 24, 2024 12:43
faaecd4
to
87ad7e1
Compare
furkansahin
force-pushed
the
multiple_fws_per_subn
branch
from
April 24, 2024 14:49
2f1a32c
to
75b2981
Compare
velioglu
approved these changes
Apr 25, 2024
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.
As we've discussed offline, creating firewalls and having an endpoint to associate it with the subnet will be added with a subsequent PR.
furkansahin
force-pushed
the
fw_to_subnet
branch
from
April 25, 2024 08:50
ea1bdab
to
4f2d6ec
Compare
furkansahin
force-pushed
the
multiple_fws_per_subn
branch
from
April 26, 2024 12:21
75b2981
to
a7bac59
Compare
furkansahin
force-pushed
the
fw_to_subnet
branch
from
April 26, 2024 12:21
4f2d6ec
to
702e980
Compare
enescakir
reviewed
May 2, 2024
byucesoy
reviewed
May 2, 2024
byucesoy
reviewed
May 2, 2024
enescakir
approved these changes
May 2, 2024
furkansahin
force-pushed
the
multiple_fws_per_subn
branch
from
May 2, 2024 16:19
a7bac59
to
07ce1ce
Compare
With this commit, our backend starts supporting Firewalls <-> PrivateSubnets many_to_many relationship. For that to work, we introduce a new model called FirewallsPrivateSubnets and maintain the relationship properly at the de/provisioning times.
furkansahin
force-pushed
the
multiple_fws_per_subn
branch
from
May 2, 2024 18:31
07ce1ce
to
f280261
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
With this commit, our backend starts supporting Firewalls <->
PrivateSubnets many_to_many relationship. For that to work, we introduce
a new model called FirewallsPrivateSubnets and maintain the relationship
properly at the de/provisioning times.