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

Custom firewall ports are not captured and trigger re-creation of firewall rules every time #137

Closed
zeebonk opened this issue Mar 2, 2022 · 5 comments

Comments

@zeebonk
Copy link

zeebonk commented Mar 2, 2022

This is not the case for firewall rules where only standard services are selected.

@dentarg
Copy link
Member

dentarg commented Mar 2, 2022

Can you explain more? Maybe you need to import firewall rules?

@dentarg
Copy link
Member

dentarg commented Mar 21, 2022

@zeebonk can you show us an example of your issue?

@zeebonk
Copy link
Author

zeebonk commented Mar 21, 2022

Hi @dentarg! I had to find a moment to continue with the work that brought this issue to light. Will come back with more details somewhere this week.

@zeebonk
Copy link
Author

zeebonk commented Mar 22, 2022

Good news, the issue was resolved with updating the provider to 1.15.1.

@zeebonk zeebonk closed this as completed Mar 22, 2022
@dentarg
Copy link
Member

dentarg commented Mar 23, 2022

v1.15.1 resolveed this issue because the validation was removed in 573866a. The validation became faulty in v1.9.3 with a092362. We will add back the validation with #141, and this time without typos and also warnings about some gotchas we found (which has been documented too).

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

No branches or pull requests

2 participants