Adam Weigert

@ahmadnassri any chance on getting this merged, as well as the node16->node20 update?

In the host.json, the category filtering is not working for the root namespace for my solution. __host.json__ ```json { "version": "2.0", "logging": { "logLevel": { "default": "Information", "MySolution": "Trace" }...

I have only noticed locally while debugging.

Just confirmed, 3.0.2931 does behave as expected. Thanks all.

@jasoth any idea when this PR will get released?

Ran across this today, did anyone find a way around this or did they have to redesign the clients that are inheriting from those types of base classes?

Is the HCL output required for this to work? jmsepath on the json would be handy here...

@ms-henglu I did try doing this with something like this but it's not filtering the output ... ```hcl terraform { required_providers { azapi = { source = "Azure/azapi" version =...

Best I can tell [from the filtering](https://github.com/Azure/terraform-provider-azapi/blob/main/utils/json.go#L159), it doesn't support properties that are arrays to filter the child values as well ...

Yes but it still stores the full response in the state file. This causes excessively large state files and we actually hit a limit because of this. Our use case...