williamjeuniaux
commented
1 week ago Hey @bbbco !
Thanks for everything you're doing I really appreciate it!
I understand a route named "Default Outbound Route" is automatically created by the API when a site is created. Trying to recreate the route will throw an exception because the route already exists, hence why having a data resource fixes that error.
However, I believe it hides the real issue and could result in having inconsistent data between two orgs. Let's say we have a source organization with Site A that has a default outbound route configured with Emergency and Network Classifications, Random Distribution Pattern & two External Trunks. Once we create that site A on a new organization through a terraform apply, site A on the target organization will have a new Default Outbound Route with default values, which are different from the source organization: different classifications, a Sequential Distribution Pattern and no external trunks.
I think default outbound routes should be exported as normal resources as it is important that they are in sync, like the other outbound routes. I believe there should be specific logic for default outbound routes, where it handles the HTTP 400 "route already exists" returned by the API when trying to create the route. Then it would retrieve the route ID and update it via PUT.
willjeuniaux-genesys
bbbco
Fixes an issue that @williamjeuniaux has seen when exporting
genesyscloud_telephony_providers_edges_site_outbound_routeresources so that Default Outbound Routes are always exported as data resources since they are always autocreated by the API.