Matt Kravetz
06/23/2023, 3:29 PMoctavia-cli
to set image versions for our Airbyte deployment's `source`s. Could anyone assist?
I have a source configuration.yml
file that initially looks like this, with the definition_version
pinned to `0.1.1`:
resource_name: Google Analytics 4 (GA4)
definition_type: source
definition_id: 3cc2eafd-84aa-4dca-93af-322d9dfeec1a
definition_image: airbyte/source-google-analytics-data-api
definition_version: 0.1.1
configuration:
credentials:
auth_type: Service
credentials_json: '*******'
property_id: '*******'
window_in_days: 1
date_ranges_start_date: '2018-01-01'
If I try updating definition_version
to 1.0.0
in the config above, importing state from my live deployment, and applying the change, the version does not update in the UI.
octavia-cli@13864765d729:/octavia$ yes N | octavia import source "Google Analytics 4 (GA4)"
The configuration octavia-cli is about to create already exists, do you want to replace it? (sources/google_analytics_4_ga4/configuration.yaml) [y/N]: ā
- Imported source Google Analytics 4 (GA4) in sources/google_analytics_4_ga4/configuration.yaml. State stored in sources/google_analytics_4_ga4/state_875ae50d-0680-4243-af7d-eaf3c815ff92.yaml
ā ļø - Please update any secrets stored in sources/google_analytics_4_ga4/configuration.yaml
octavia-cli@13864765d729:/octavia$ octavia apply -f sources/google_analytics_4_ga4/configuration.yaml
š - Google Analytics 4 (GA4) exists on your Airbyte instance according to your state file, let's check if we need to update it!
š“ - Did not update because no change detected.
I am able to use this workflow to adjust other config settings (window_in_days
, credentials_json
, etc), but it seems the definition_version
changes aren't taking. Any help getting this working would be much appreciated!user
06/23/2023, 3:29 PMuser
06/23/2023, 3:29 PMMatt Kravetz
06/26/2023, 6:05 PM