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

Feature Request - Statically Allocate BGP peering IPs (similar to #562) #563

Open
fengwang523 opened this issue Feb 17, 2024 · 0 comments
Open

Comments

@fengwang523
Copy link

This request is similar to #562

For border leaf BGP peering sessions with generic system, the same challenge applies.

The BGP peering IPs are allocated by a role "to_generic_link_ips" to an IP pool mapping. Here is an example code:

resource "apstra_datacenter_resource_pool_allocation" "tf_rz_ipv4_external_allocation" {
count = var.rz_ipv4_external_pool != null ? 1 : 0
blueprint_id = var.bp_id
role = "to_generic_link_ips"
pool_ids = [apstra_ipv4_pool.tf_rz_ipv4_external_pool[0].id]
routing_zone_id = apstra_datacenter_routing_zone.tf_rz.id
}

The peering IPs are dynamically allocated, therefore the values are not known until terraform apply and they would change upon destroy and re-apply.

The feature request is that to be able to hardcode the peering IPs using values from the IP pool.

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

1 participant