Raúl Sánchez

This is not intentional, `user_principal_id` should work properly. Have you customized your openldap user/group schemas??

> I tried with default schemas and with customised ones too. If I enter the username on the UI (cluster / Members / add member) it does find the user...

As mentioned, i guess this may be an issue of not using `user_id` argument (UI is setting it). Has the openldap `user_principal_id` been logged in Rancher?? Have you tested tf...

> This is the same issue as #225 > > Forcing users to log in first and then using their user_id as suggested is not very practical, especially in larger...

Hi @ruzickap , the tf provider is just calling the Rancher API to create or remove the cluster. If the terraform destroy is not getting any error, may be the...

@caiconkhicon , template revisions are tricky due to they are managed by a terraform list, what it means that it's dependant of the order. Provider is shifting the list to...

@p4ranoidandro1d , `values` argument should be intended to provide a value.yaml replacement. Not needed to fully explain the behaviour on your side, but in order to reproduce the issue, could...

The `rancher2_app_v2` values comparison is not done as string. The keys order doesn't matter as the yaml content is unmarshaled to a `map[string]` before `reflect.DeepEqual` comparison, https://github.com/rancher/terraform-provider-rancher2/blob/master/rancher2/schema_app_v2.go#L102 . Agreed that...

@julienym , alphabetically order has nothing to do for the diff generation (although the tf diff visualization may be confuse see my previous comment), any other diff should be there....

> Well, fact is, this makes reading the diff and actually finding the difference impossible. It doesn't keep the order. Simplest fix would be to sort the local values for...