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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

GOOGLE COMPUTE REGIONAL SECURITY POLICY POLICY/CLASS DOESN'T EXIST #3610

Open
1 task
cyber-francis opened this issue May 2, 2024 · 2 comments
Open
1 task
Labels
enhancement New feature or request

Comments

@cyber-francis
Copy link

Description

There is currently no compute regional security policy/rule class.

References

N/A

Help Wanted

  • I'm interested in contributing a fix myself

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@cyber-francis cyber-francis added enhancement New feature or request new Un-triaged issue labels May 2, 2024
@cyber-francis cyber-francis changed the title COMPUTE REGIONAL SECURITY POLICY AND RULE GOOGLE COMPUTE REGIONAL SECURITY POLICY POLICY/CLASS DOESN'T EXIST May 3, 2024
@ansgarm
Copy link
Member

ansgarm commented May 13, 2024

Hi @cyber-francis 馃憢

Could you share which version of CDKTF, the google (pre-built?) provider you use and on which language?

If it is available in Terraform, it should be available in CDKTF as well, so you might be on an outdated version somehow 馃檪

@ansgarm ansgarm added waiting-on-answer and removed new Un-triaged issue labels May 13, 2024
@cyber-francis
Copy link
Author

I was able to use the google beta version. But, there is another problem: the regional security policy doesn't implement a default deny, instead it implements a default allow.

Please, are you guys aware of this, and is there a fix coming soon or already out there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants