-
Notifications
You must be signed in to change notification settings - Fork 85
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
Policy Datasources for leveraging built-in services #696
Comments
Actually, seems like terraform's "output" resource help here
but the names don't match what is seen in the GUI or even in the API
So is ICMP-ALL object visible in API and GUI returned by TF as "ICMP-entry"? Seems odd. And conversely, "ICMP-entry" is not a valid name that can be found in the GUI
|
Hi @akhomyakov, unfortunately these data sources are based on old-style MP API, not policy API, so they won't do what you expect. These were added for a specific customer that cannot use policy API due to very specific feature set they are using. |
I see. This suggests that these two will never come out of beta. I am looking for a way to import all existing service objects and groups rather than import them one by one. In other words, NSXT comes with a long list of prebuilt services to be used in the security policy like ICMPv4 and so on. Is there a sane way to import them all in one go or it's a one by one type of endeavor only? |
For now there are no parallel data sources for policy APIs, but seems like people are asking for it. So these are on the roadmap. For now though prebuilt data sources need to be imported one by one. |
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. 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! |
bump |
These data sources allows the retrieval of the entire tables from NSX to save multiple calls to the backend. Fixes: vmware#696 Signed-off-by: Kobi Samoray <[email protected]>
These data sources allows the retrieval of the entire tables from NSX to save multiple calls to the backend. Fixes: vmware#696 Signed-off-by: Kobi Samoray <[email protected]>
These data sources allows the retrieval of the entire tables from NSX to save multiple calls to the backend. Fixes: vmware#696 Signed-off-by: Kobi Samoray <[email protected]>
These data sources allows the retrieval of the entire tables from NSX to save multiple calls to the backend. Fixes: vmware#696 Signed-off-by: Kobi Samoray <[email protected]>
Moving this issue to 3.9.0 due to low priority and the fact that we are close to 3.8.0 release |
Hi folks,
Looking at the nsxt_ns_groups and nsxt_ns_services data resources (currently in Beta) they appear like exactly what is needed to make use of built in services and so on.
What I can't figure out is how to refer to items imported. Is there a way to output the content of what is imported?
Just using the API doesn't seem to yeild the right results
The text was updated successfully, but these errors were encountered: