-
Notifications
You must be signed in to change notification settings - Fork 54
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
Added the egress rules and create_default_rules option to firewall #120
Conversation
…fault rules when you create a firewall Signed-off-by: Alejandro J. Nuñez Madrazo <[email protected]>
Signed-off-by: Alejandro J. Nuñez Madrazo <[email protected]>
We should probably bump up the go version in github action to match the one in go.mod |
Signed-off-by: Alejandro J. Nuñez Madrazo <[email protected]>
@RealHarshThakur Done |
.github/workflows/go.yml
Outdated
runs-on: ubuntu-latest | ||
strategy: | ||
matrix: | ||
go-version: [1.14.x, 1.15.x, 1.16.x, 1.17.x] |
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.
I don't think we need to test all versions with GHA. Just the one we are using for this provider. It's because there's no client/other package depending on this
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.
OK
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.
I will keep this [1.16.x, 1.17.x]
Seems like the build is failing from 1.16? |
Signed-off-by: Alejandro J. Nuñez Madrazo <[email protected]>
Signed-off-by: Alejandro J. Nuñez Madrazo <[email protected]>
Added the egress rules and the option to avoid the creation of the default rules when you create a firewall