exclude data activation destinations from upgrade tests #69781
+12
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
see also https://github.com/airbytehq/airbyte-enterprise/pull/314 - we need to add a param for the enterprise repo.
there's probably more elegant ways to do this (e.g. parse metadata.yaml to check for
connectorSubtype: api+connectorType: destination) but that would be a lot more work for no real benefit 🤷 happy to point claude at that, if we think it's useful, but IMO this is sufficientcompletely untested :P going to just let the cron run overnight and hope it works