Debugging env_vars in local Airbyte deployment

Slack Knowledge Base Q&A API, Terraform and Other Topics
, , , ,
1

Summary

User is experiencing issues with setting environment variables in their Airbyte deployment using abctl where the configured retries are not being recognized, leading to a default behavior of 5 retries on sync failures. Requesting guidance on debugging this issue.


Question

Hello!
I’m trying to add env variables to the airbyte running locally using abctl in my values.yaml file:

  env_vars:
    - name: SYNC_JOB_MAX_ATTEMPTS
      value: "1"
    - name: SYNC_JOB_RETRIES_PARTIAL_FAILURES_MAX_TOTAL
      value: "1"
    - name: SYNC_JOB_RETRIES_PARTIAL_FAILURES_MAX_SUCCESSIVE
      value: "1"
    - name: SYNC_JOB_RETRIES_COMPLETE_FAILURES_MAX_SUCCESSIVE
      value: "1"
    - name: SYNC_JOB_RETRIES_COMPLETE_FAILURES_MAX_TOTAL
      value: "1"```
but for some reason airbyte does not see them and retries 5 times in case sync failed, how to debug why it doesn't use my env_vars?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1732937386756879) if you want
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
['abctl', 'env-variables', 'values.yaml', 'airbyte', 'local-deployment']
</sub>
2

This is the entire values.yaml File?

3

hey <@U01MMSDJGC9> thank you for the question, no it was not a full yaml fill, just a part. I found out what was my mistake, the correct values.yaml should look like this:

  env_vars: {"SYNC_JOB_MAX_ATTEMPTS":"1","SYNC_JOB_RETRIES_PARTIAL_FAILURES_MAX_TOTAL":"1","SYNC_JOB_RETRIES_PARTIAL_FAILURES_MAX_SUCCESSIVE":"1","SYNC_JOB_RETRIES_COMPLETE_FAILURES_MAX_SUCCESSIVE":"1"}```
It will be great if you can add this example to the documentation - it will save some time to other people