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

[Enhancement]: Add interface location.broadcast_domain parameter #305

Open
acch opened this issue Sep 30, 2024 · 1 comment · May be fixed by #337
Open

[Enhancement]: Add interface location.broadcast_domain parameter #305

acch opened this issue Sep 30, 2024 · 1 comment · May be fixed by #337
Labels
enhancement New feature or request
Milestone

Comments

@acch
Copy link

acch commented Sep 30, 2024

Description

Ability to configure location.broadcast_domain for SVM-scoped interfaces

Affected Resource(s) and/or Data Source(s)

  • netapp-ontap_network_ip_interface

Potential Terraform Configuration

# example IP interface
resource "netapp-ontap_network_ip_interface" "example" {
  cx_profile_name = "cluster1"
  name            = "testme"
  svm_name        = "ansibleSVM"

  ip = { ... }

  location = {
    home_node = "node1"
    broadcast_domain = {
      name = "bd1"
    }
  }
}

References

Would you like to implement a fix?

Yes

@acch acch added the enhancement New feature or request label Sep 30, 2024
@carchi8py carchi8py moved this from Future to 2.1 in Terraform for ONTAP Roadmap Sep 30, 2024
@carchi8py carchi8py added this to the 2.1 milestone Sep 30, 2024
@acch
Copy link
Author

acch commented Oct 21, 2024

Do you have any objections with the proposed changes? If not, then I will go ahead and start working on a PR to implement the new location.broadcast_domain parameter for IP interface data source and resource...

@acch acch linked a pull request Nov 20, 2024 that will close this issue
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
Status: 2.1
Development

Successfully merging a pull request may close this issue.

2 participants