Ivan Zaitsev
It is also possible to implement similar logic on client side, but it uses reflection and is not so good as native implementation. ``` registerSubtypes(Subtype.class, ...); private void registerSubtypes(Class... classes)...
What is the status of this issue?
@xuzhang3 Still not possible to extract "service_principal_id" from "azuredevops_serviceendpoint_azurerm" in some automatic way?
@xuzhang3 I saw it from the messages above. This way it would retrieve `serviceprincipalid` only in case if it was specified in `credentials` block for `azuredevops_serviceendpoint_azurerm`. It would not return...
Same problem when in the "required_resource_access" block "resource_app_id" should be specified as self "application_id".
Any update on this feature?
@TwiN It would be good to have a feature to restrict specific group based on security. For example in OIDC there is a claim called `groups` which can be used...
I think that mockserver could still continue using Java 8 while mockserver-spring-test-listener Java version cloud be upgraded to 17 to support Spring Boot 3
As workaround for fixing this: before calling `registration.getServiceInstance()` this line should be called `registration.setPort(0);` For example: ``` @Bean public DefaultCandidate bean(ServiceInstanceRegistration registration) { registration.setPort(0); return return new DefaultCandidate(registration.getServiceInstance().getId(), "default"); }...
I think it can be closed. It is possible to disable validation using `liquibase.mongodb.supportsValidator=false` in `liquibase.properties`