-
Notifications
You must be signed in to change notification settings - Fork 1
feat: add workaround for groups #293
Conversation
|
/run pipeline |
main.tf
Outdated
| ## This block is for if host_flavor IS set to specific pre-defined host sizes and not set to "multitenant" | ||
| dynamic "group" { | ||
| for_each = local.host_flavor_set ? [1] : [] | ||
| for_each = local.host_flavor_set && var.member_host_flavor != "multitenant" && !local.recovery_mode ? [1] : [] |
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.
There is no plan type that supports multi tenant (for EDB, it is enterprise and isolated only). So the structure here is a bit different, remove && var.member_host_flavor != "multitenant"
main.tf
Outdated
| ## This block is for if host_flavor IS NOT set | ||
| dynamic "group" { | ||
| for_each = local.host_flavor_set ? [] : [1] | ||
| for_each = local.host_flavor_set && var.member_host_flavor == "multitenant" && !local.recovery_mode ? [1] : [] |
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.
There is no plan type that supports multi tenant (for EDB, it is enterprise and isolated only). So the structure here is a bit different, remove && var.member_host_flavor == "multitenant"
main.tf
Outdated
| host_flavor { | ||
| id = var.member_host_flavor |
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.
The structure here should not be changing. This was the block that supported the old style, no host_flavor.
|
/run pipeline |
shemau
left a comment
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.
LGTM
|
🎉 This PR is included in version 1.8.13 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
#283
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
Add workaround to ignore groups config when provisioning instance using backup CRN
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers