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

Add selectel_dbaas_firewall_v1 resource #278

Merged
merged 4 commits into from
Aug 12, 2024

Conversation

Gogen120
Copy link
Contributor

Description

Make firewall field for datastore resources deprecated. Because, we cannot change firewall state during creation of the datastore, only after. For example, if we create a datastore with defined firewall, then it will be applied only after the second run of terraform apply. That's an unexpected behavior. It can be fixed with introducing a separate selectel_dbaas_firewall_v1 resource to manage datastore's firewall, that attached to datastore with datastore_id field

Relations

Closes #277

- Make firewall field for datastore resources deprecated. Because, we
cannot change firewall state during creation of the datastore only after
- Add a new selectel_dbaas_firewall_v1 resource to manage datastore's
firewall
@Gogen120 Gogen120 force-pushed the add_dbaas_firewall_resource branch from 19fa651 to 8f0654e Compare May 23, 2024 08:23
@TawR1024 TawR1024 requested a review from Vasilek15 August 5, 2024 12:42
@TawR1024 TawR1024 merged commit 06b584f into selectel:master Aug 12, 2024
8 checks passed
@Gogen120 Gogen120 deleted the add_dbaas_firewall_resource branch September 20, 2024 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DBaaS datastore's firewall rules are changed only after second run of terraform apply
3 participants