Custom Identity Provider with extra custom config about terraform-provider-keycloak HOT 4 CLOSED

The solution might be in writing a custom Marshal and Unmarshal method, where additional config will come from an extra_config field in the idp resource

func (f *IdentityProviderConfig) UnmarshalJSON(data []byte) error {
	f.ExtraConfig = map[string]interface{}{}
	err := json.Unmarshal(data, &f.ExtraConfig)
	if err != nil {
		return err
	}
	knownkey, ok := f.ExtraConfig["knownkey"].(string)
	if !ok {
		return errors.New("knownkey must exist and be a string")
	}
	f.KnownKey = knownkey
	delete(f.ExtraConfig, "knownkey")
	return nil
}

func (f *IdentityProviderConfig) MarshalJSON() ([]byte, error) {
	out := map[string]interface{}{}
	for k, v := range f.ExtraConfig {
		out[k] = v
	}
	out["knownkey"] = f.Knownkey
	return json.Marshal(out)
}

something like this

from terraform-provider-keycloak.

I like the idea of the extra_config field, although I don't actually use identity providers in Keycloak so I am not sure how valuable my opinion is.

@AndrewChubatiuk implemented most (if not all) of this, so I'd defer to his opinion or anyone else who actually uses this. Any thoughts here?

from terraform-provider-keycloak.

@mrparkers @tomrutsaert
I like idea of having one keycloak_identity_provider resource for all types of providers with validation schemas for config attribute map for all identity provider types except custom. And in this case IdentityProviderConfig struct can be replaced with map[string]interface

from terraform-provider-keycloak.

Keep in mind, that most custom implementations will build upon or extend an existing identity provider type, and thus also want the those existing identity provider attributes with validation.
Therefor I went with the extra_config within config. I have implemented everything in identity_provider built only extended the resource_keyclaok_oidc_identity_provider
It should be minimal effort to do the same for resource_keycloak_saml_identity_provider.
(I did not do the saml part, because making a working test would take time)
@mrparkers and @AndrewChubatiuk Please take a look at PR: #137

from terraform-provider-keycloak.