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

Data source data "nsxt_ns_groups" "map" { } is not working in version 3.2.8 #776

Open
Nareshcbit opened this issue Aug 2, 2022 · 4 comments

Comments

@Nareshcbit
Copy link

Describe the bug

Error: This data source is not supported with given provider settings

│ with data.nsxt_ns_groups.map,
│ on main.tf line 34, in data "nsxt_ns_groups" "map":
│ 34: data "nsxt_ns_groups" "map" {

Reproduction steps

1. terraform {
  required_providers {
    nsxt = {
      source = "vmware/nsxt"
      version = "3.2.8"
    }
  }
}
2. data "nsxt_ns_groups" "map" {
}
3. run terraform plan

...

Expected behavior

This data source is expected to build a "name to uuid" map of the whole NS Group table.

Additional context

No response

@Nareshcbit Nareshcbit added the bug label Aug 2, 2022
@annakhm
Copy link
Collaborator

annakhm commented Aug 2, 2022

Hi @Nareshcbit, are you running against VMC environment? Manager resources are not supported on VMC.

@Nareshcbit
Copy link
Author

Nareshcbit commented Aug 4, 2022

@annakhm yes I am running against VMC.

Any idea if it is coming in the future releases? Because, if it is coming soon we would like to use the native data resources than using custom approaches.

@annakhm annakhm removed the bug label Aug 4, 2022
@annakhm
Copy link
Collaborator

annakhm commented Aug 4, 2022

Last time we checked, VMC did not support Manager API that is required to expose Manager objects in the provider (as opposed to policy objects).
Would you be happy to use nsxt_policy_groups data source if it existed? This could be a feature request.

Copy link

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!

@github-actions github-actions bot added the stale label Mar 29, 2024
@ksamoray ksamoray removed the stale label Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants