Improve data sources experience in the provider

[zbuchheit]

Is your feature request related to a problem? Please describe. Currently doing a data source lookup is cumbersome. For example, if I want to look up meraki_networks_switch_access_policies the data source object responds with an object containing attributes .item and .items, with the actual data nested underneath these attributes. This structure introduces complexity and inefficiency in accessing the desired data.

Describe the solution you'd like Alternatively, you could break data sources into two version. Such as meraki_networks_switch_access_policy and meraki_networks_switch_access_policy_list to accomplish a more ergonomic user experience. This would also prevent having to handle .item and .items and you could just expose the data without nesting.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

[fmunozmiranda]

We will take it into account for a future version, thank you very much for the suggestion.

[zbuchheit]

great! Thanks! 😄