We are attempting to import idp_adfs configuration into CICD and are running into an issue with slo_binding value.
The current slo_binding value in our Genesys Cloud Org is "urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" - we do not want to change this value, we just want idp_adfs to be tracked in CICD.
When we try to import idp_adfs into CICD, we get the following error:
Error: expected slo_binding to be one of ["HTTP Redirect" "HTTP Post"], got urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect
Could you please advise how we can import this object into CICD without changing it in Genesys Cloud?
Sorry for the delay in questioning. Thanks for reaching out. The idp_adfs configuration is one of the more obscure components we have in CX as Code (I think you are the first to ask a question since we released it).
Can you document the steps you are using to do the import for me? I will open a ticket on it and get someone from my team to look at this in our next Sprint (which starts on Tuesday). These steps (CX as Code commands, Terraform import) command the higher the likelihood
Thanks,
John Carnell
Director, Developer Engagement
P.S.
Sorry for the delay on this. We had a major internal developer conference two weeks ago where most of my team was at and we are just getting caught up on your backlog. Thanks for reaching out to your TAM Jim; he helps us bring visibility to these issues.
The import command is just a standard command:
terraform import {resource_name} {GC ID}
To remove: terraform state rm {resource_name}
The issue seems to be that the TF Provider for GC is validating the slo_binding and not recognizing a valid value which was set in the object when the object was created through the UI.