Hello all :slightly_smiling_face: Quick feedback o...
# give-feedback
s
Hello all 🙂 Quick feedback on Helm Chart V2 migration (that took me 1 day because of not having the correct values.yml in the documentation 😿). •
global.storage.type
changed from
GCS
in Chart V1 to
gcs
in Chart V2 • For secret management: ◦ the key in Chart V2
global.storage.gcs.credentialsJsonPath
is not correct for
gcs
(I could not make it work) â—¦ the key in Chart v2 is
global.storage.gcs.credentialsJsonSecretKey
in combinasion with
global.storage.secretName
So if it can help some people trying the migration: • In V1 I had; ◦
global.storage.type: 'GCS'
â—¦
global.storage.gcs.storageSecretName: 'airbyte-config-secrets'
â—¦
global.storage.gcs.credentialsPath: '/secrets/gcs-log-creds/gcp.json'
• In V2 I could make work ◦
global.storage.type: '*GCS*'
â—¦
global.storage.gcs.*secretName*: 'airbyte-config-secrets'
â—¦
global.storage.gcs.*credentialsJsonSecretKey*: '*gcp.json*'
I hope it can help 🙂
l
Hi! I'll try to send all the problems I'm encountering after the upgrade here so that everyone sees it and (hopefully) don't suffer as we did
## Upgrading Problems • undocumented prop
global.storage.gcs.credentialsJsonSecretKey
when translating v1 logging storage config. Docs only show(ed when I upgraded) a way to configure the actual secret on values.yaml • had problems with database
global.database
fields, where I think temporal was trying to deploy to the airbyte database instead of its own. Had to add temporal environment variables so that it would point to the correct databases (
temporal
and
temporal_visibility
) • (still not solved) after the upgrade, I'm seeing a lot of temporal logs
io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: namespace rate limit exceeded... leads me to think I'll have to tinker with temporal variables
---
## The aftermath ## Problem 1: custom builder pagination issues • suddenly, the "inject into" body or header all vanished • after I re-added them, the tests failed with a gigantic stacktrace • found out that after re-adding the fields, the builder didn't "clean" the old
paginator.page_size_option.field_name
field and added the new
paginator.page_size_option.field_path[*]
field. This is against the spec, since only one or the other should be specified • had to manually edit the yaml removing the old field ## Problem 2: custom builder plain text doesn't work Opened this issue. All the XML requests broke ## Problem 3: Async streams record selector When I set the "Download tab" record extractor in the UI, it fills the
AsyncRetriever.record_selector
This has absolutely no effect Had to manually fill
AscynRetriever.download_extractor
in the yaml editor to have the desired effect