Closed vinay-gopalan closed 6 months ago
One question I have is if we should consider not removing the AD resources/datasources for now. My understanding is there has been some friction with some customers migrating from AD to LDAP. I am not sure if removing them would cause more pain for customers that haven't found a good migration path? I think @austingebauer may have some more context here?
That's right @fairclothjm. I would suggest leaving the AD resources in. We might end up leaving the AD secrets engine in Vault with the disclaimer that we aren't adding new features to it instead of our original plan to completely remove it. It's still a bit TBD as we work through migrations with customers.
One question I have is if we should consider not removing the AD resources/datasources for now. My understanding is there has been some friction with some customers migrating from AD to LDAP. I am not sure if removing them would cause more pain for customers that haven't found a good migration path? I think @austingebauer may have some more context here?
That's right @fairclothjm. I would suggest leaving the AD resources in. We might end up leaving the AD secrets engine in Vault with the disclaimer that we aren't adding new features to it instead of our original plan to completely remove it. It's still a bit TBD as we work through migrations with customers.
Sounds good, thanks for the feedback y'all! I'll add the AD resources back in
Closing as we will not be pursuing multiplexing at this time.
Removes all fields, resources and data sources marked as
Deprecated
in preparation for the major version release with the multiplexed providerList of deprecations —