Hi @kapa.ai I'm trying to update my local airbyte os installation with abctl. But i get this error: couldn't find key DEFAULT_MINIO_ACCESS_KEY in Secret airbyte-abctl/airbyte-abctl-airbyte-secrets

It seems like you're encountering an issue where the

DEFAULT_MINIO_ACCESS_KEY

is not found in the Kubernetes secret

airbyte-abctl-airbyte-secrets

. This issue was also reported in a [Github issue](https://github.com/airbytehq/airbyte/issues/39604) where the user was unable to find the

DATABASE_USER

key in the secret. The user in the Github issue found a workaround by patching the Kubernetes secret to add the missing key immediately after deployment. Here's the command they used:

shell kubectl patch secret airbyte-airbyte-secrets \   --namespace=production-hm-airbyte \   --patch="{\"stringData\":{\"DATABASE_USER\":\"airbyte_user\"}}"

You can try a similar approach for your issue. Replace

DATABASE_USER

with

DEFAULT_MINIO_ACCESS_KEY

and

airbyte_user

with the actual value of your MinIO access key. Also, replace

production-hm-airbyte

with

airbyte-abctl

which is your namespace. Please note that this is a workaround and it would be better to understand why the key is not being added to the secret during the deployment. You might want to check your

values.yaml

file and ensure that it's correctly configured. You can refer to the [Airbyte documentation](https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart#customizing-your-installation-with-a-values-file) for more details on how to customize your installation with a

values.yaml

file. If the issue persists, I recommend raising an issue in the [Airbyte Github repository](https://github.com/airbytehq/airbyte/issues) for further assistance.

@kapa.ai fixed it. Another question; I have an api that wants me to request incrementally with fields from and to. And this must equate one day although from is 1sep and to is 2sep. So you'll only receive 2 sep from that request. P1D obviously generates a wrong request. But I'm afraid that using P2D will mean it does 1-2, then 3-4, while it should be 1-2, 2-3, 3-4, 4-5. what kind of increment would work for me in the connector builder?

A message from kapa.ai

In the Connector Builder, you can use the Incremental Sync feature to pull only the data that has changed since the previous sync. This is especially useful when there are a large number of records to sync or the API has tight request limits. For your specific case, you might want to use the "DatetimeBasedCursor" incremental sync strategy. This strategy allows you to specify a date/time field that defines when a record was last updated (the "cursor field"). The connector will then only fetch records that have a cursor field value greater than the last sync's cursor value. However, the Connector Builder currently does not support a built-in way to increment the date by one day for each request. You might need to implement this logic in your connector code. If none of the built-in pagination methods (Offset Increment, Page Increment, Cursor Pagination) work for your API, you might need to use the low-code CDK or Python CDK to implement your custom logic. Here are the relevant documentation links for more information: - [Incremental Sync](https://docs.airbyte.com/connector-development/connector-builder-ui/incremental-sync) - [Low-code CDK Overview](https://docs.airbyte.com/connector-development/config-based/low-code-cdk-overview) - [Python CDK](https://docs.airbyte.com/connector-development/cdk-python/)

@kapa.ai Is there really no way to have the interval act accordingly? I'm afraid P2D will skip over a day instead of what I'm looking for

A message from kapa.ai

Based on the information provided in the knowledge sources, the "Step" and "Cursor granularity" settings in the Connector Builder's Incremental Sync feature are used to determine the size of the time intervals for each request. The "P1D" value represents a one-day interval, and "P2D" represents a two-day interval. However, the Connector Builder currently does not support overlapping intervals (e.g., 1-2, 2-3, 3-4, etc.) as you described. If you set the "Step" and "Cursor granularity" to "P2D", the Connector Builder will likely create non-overlapping two-day intervals (e.g., 1-2, 3-4, etc.). To achieve the overlapping intervals, you might need to implement custom logic in your connector code. This could involve using the low-code CDK or Python CDK to customize the pagination logic. Here are the relevant documentation links for more information: - [Incremental Sync](https://docs.airbyte.com/connector-development/connector-builder-ui/incremental-sync) - [Low-code CDK Overview](https://docs.airbyte.com/connector-development/config-based/low-code-cdk-overview) - [Python CDK](https://docs.airbyte.com/connector-development/cdk-python/) If you need further assistance, I recommend reaching out to the Airbyte community on [their forum](https://discuss.airbyte.io/) or [GitHub](https://github.com/airbytehq/airbyte).