TF Error With Schedules - Continued

Genesys Cloud Integrations
1

Hello,

We are still experiencing the issue below with Provider 1.52.0

TF Error with schedules - Genesys Cloud Integrations - Genesys Cloud Developer Forum

Do you please have any updates?

Thank you.

2

Hello again,

After some more investigating, I think we may have something - your original assessment seems to be correct - "Public API we call mutates the data"

What seems to be happening:

If you have a weekly schedule for a Saturday, the start date for that schedule must be a Saturday.

It cannot be any other day as the API Call seems to set that value for the first Saturday after the date specified in Start Date.

If the date in TF is set to anything other than a Saturday, and the API Call then changes it to Saturday, that's where the TF error "Error: mismatch on attribute start" seems to be coming from.

The two options I see are, either:

  • Perform this Validation in Plan stage and Report on it, not just during Deployment
  • API not to change the specified Start Date

Thank you.

3

Hi JMakacek,

Thanks for the additional information. I will need to return it to the API team and get their take. If they concur we will need to determine whether or not the change should happen in the API or in Terraform. Is this issue a blocker for you or is it just forcing a create/tear down of a resource (which can be annoying) or is it breaking a dependency (because the new resource has a new GUIID).

The validation approach will be the quickest to implement as the Terraform provider is in my direct area of responsibility. You caught us at a good time as we are just getting ready for our Sprint next week.

Thanks,
John Carnell
Director, Developer Engagement

4

Thank you John.

Yes, references for tainted objects is one of the issues, and the fact that this only happens during Deployment is another.

We have limited Deployment window for Production, and these errors come as a surprise which then causes confusion about how to proceed, and how long it will take, so that the change can be completed off-hours.

Thank you again.

5

Hi JMakacek,

No worries. I asked our team lead for the group to create a ticket to further investigate.

  • John
7

Hi @jmakacek

We just merged a fix for this, which you will see released on v1.56.0 in early January, after the Christmas period.

Thanks for raising the issue.

-Charlie

8

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.