You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, these attributes are accessed through the egress_config attribute, which is strangely nested in lists. This is how the whole databricks_mws_network_connectivity_config object looks like:
The section should describe the schema of the object, so one can figure how any necessary attribute should be access. For instance, to reach the list of subnets ids associated with the NCC, you currently need this path: databricks_mws_network_connectivity_config.this.egress_config[0].default_rules[0].azure_service_endpoint_rule[0].subnets
List of things to potentially add/remove
This is a list of things to manipulate in the docs:
Describe the attributes schema in detail
Ideally fix the issue upstream, so that the databricks_mws_network_connectivity_config object's schema directly follows the corresponding REST endpoint response's schema.
Important Factoids
References
The text was updated successfully, but these errors were encountered:
Affected Resource(s)
According to the documentation, subnet configuration of an NCC resource is accessed through
default_rules.azure_service_endpoint_rule
.However, these attributes are accessed through the
egress_config
attribute, which is strangely nested in lists. This is how the wholedatabricks_mws_network_connectivity_config
object looks like:Expected Details
The section should describe the schema of the object, so one can figure how any necessary attribute should be access. For instance, to reach the list of subnets ids associated with the NCC, you currently need this path:
databricks_mws_network_connectivity_config.this.egress_config[0].default_rules[0].azure_service_endpoint_rule[0].subnets
List of things to potentially add/remove
This is a list of things to manipulate in the docs:
databricks_mws_network_connectivity_config
object's schema directly follows the corresponding REST endpoint response's schema.Important Factoids
References
The text was updated successfully, but these errors were encountered: