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

Bulk import feature for nsx-t - [services and groups] into terraform #1061

Open
chanakanissanka opened this issue Dec 11, 2023 · 1 comment
Labels
enhancement Enhancement stale Stale

Comments

@chanakanissanka
Copy link

chanakanissanka commented Dec 11, 2023

Is your feature request related to a problem? Please describe.

This is related to the current issue we are facing regarding imports. To give a quick update on this, we are setting up VMC on AWS and already migrated 10k+ groups + 3k+ services into NSX-T manager from on-prem ASA. Now we need to find a way to bring these objects into our terraform pipeline.

Rather than doing it one by one, import those groups and services. Is there any proposed automated way of doing it? If someone has done similar before, can we get some idea please

Describe the solution you'd like

if I import those 3k services, it will repeat this block 3k times and then add a dynamic block or something later. Please let me know if there is a better way of doing this.

The solution we would like is: Import pre-created services and groups into the Terraform pipeline without much of a hassle.

resource "nsxt_policy_service" "service_import" {
display_name = "XXXXXXXXXX"
#id = "aaaaaaa"
#nsx_id = "bbbbbbbbb"
#path = "/infra/services/cccccccc"
#revision = 0

l4_port_set_entry {
destination_ports = [
"2040",
]
protocol = "TCP"
source_ports = []
}

}

Describe alternatives you've considered

If I can get some perspective on alternatives, that would be great.

Additional context

No response

@chanakanissanka chanakanissanka added the enhancement Enhancement label Dec 11, 2023
Copy link

github-actions bot commented Dec 6, 2024

'Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context.
Thank you!'

@github-actions github-actions bot added the stale Stale label Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement stale Stale
Projects
None yet
Development

No branches or pull requests

1 participant