Closed ksamoray closed 1 month ago
/test-all
/test-all
/test-all
/test-all
/test-all
This PR does not cover the provider-defined VPC scope yet, correct?
This PR does not cover the provider-defined VPC scope yet, correct?
Indeed - the provider-level VPC specification is a global, non per-resource change.
/test-all
Hi, a quick maybe dumb question: does this series of change support data_source_nsxt_policy_security_policy
and data_source_nsxt_policy_gateway_policy
? Looks like for Get with ID, it's handled, but without ID, it still lists the domain
🤔
Hi, a quick maybe dumb question: does this series of change support
data_source_nsxt_policy_security_policy
anddata_source_nsxt_policy_gateway_policy
? Looks like for Get with ID, it's handled, but without ID, it still lists thedomain
🤔
@qiyueyao I haven't got to handle these data sources yet but yeah - unless they use search API, they'll be affected by this change as the API wrapper is modified.
I believe that I should add a check to the DS, that the VPC is not specified - as these datasources aren't supposed to serve VPC.
VPC should have a pair of data_source_nsxt_policy_vpc.*
datasources.
/test-all
/test-all
LGTM. There are some doc fixes needed, but feel free to address them in one of the following PRs if you prefer
/test-all
Implement the resource for east-west VPC security policy.