Jason Maddern
06/16/2023, 2:33 AMoctavia apply for a connection, it updates, stores the new state. But if I immediately re-run apply for the same connection it says the state needs to be updated and re-runs.
I have just updated the state, I can see the state locally being updated. So it should say "no change needed". Any ideas on how I deal with this one?kapa.ai
06/16/2023, 2:33 AMkapa.ai
06/16/2023, 2:34 AMoctavia apply multiple times for the same connection results in unnecessary updates. This could be due to Airbyte adding some extra changes after applying the local config, as mentioned in this [tutorial](https://airbyte.com/tutorials/version-control-airbyte-configurations). To avoid this difference, you should import the Airbyte config locally and commit these fields. Here's an example of the output you might see when running `octavia apply`: 👀 - Here's the computed diff (🚨 remind that diff on secret fields are not displayed): + - Item root['schedule_data'] added to dictionary. - - Item root['schema_change'] removed from dictionary. - - Item root['notify_schema_changes'] removed from dictionary. - - Item root['non_breaking_changes_preference'] removed from dictionary. - - Item root['geography'] removed from dictionary. E - Value of root['schedule_type'] changed from "manual" to "basic". In this example, you'll notice differences related to your local configuration changes (root['schedule_data'] and root['schedule_type']). The rest of the differences come from Airbyte adding some extra changes after applying the local config. To resolve this issue, try importing the Airbyte config locally and committing these fields. If you still face the problem, consider reaching out to the Airbyte community on their [Slack](https://airbytehq.slack.com) or [forum](https://discuss.airbyte.io) for further assistance.