Align strict-encrypt connector version with the actual connector

[grishick]

Change the version of destination-oracle-strict-encrypt to match the version of destination-oracle connector

[edgao]

ugh, I always forget these variants exist.

I can't find the specifics, but didn't liren/davin make this process better during hackdays?

[ryankfu]

LGTM, we talked about this but currently the build process doesn't allow for multiple updates to the several Dockerfiles at once, right?

I remember this was my assignment from yesterday so that's my fault I dropped the ball. It's definitely a hassle to have to make multiple PRs when I can definitely see this as an auto generated from from the general database version or would that cause issues because it would be important to separate the versioning?

[grishick]

ugh, I always forget these variants exist.

I can't find the specifics, but didn't liren/davin make this process better during hackdays?

I don't think their project is finished yet

[grishick]

LGTM, we talked about this but currently the build process doesn't allow for multiple updates to the several Dockerfiles at once, right?

I remember this was my assignment from yesterday so that's my fault I dropped the ball. It's definitely a hassle to have to make multiple PRs when I can definitely see this as an auto generated from from the general database version or would that cause issues because it would be important to separate the versioning?

ultimately, we want to get rid of these "***-strict-encrypt" connectors in favor of a solution that @tuliren and @davinchia came up with during the last hackathon

[grishick]

/publish connector=destination-oracle-strict-encrypt run-tests=false

🕑 Publishing the following connectors:
destination-oracle-strict-encrypt
https://github.com/airbytehq/airbyte/actions/runs/2693687196

Connector	Did it publish?	Were definitions generated?
destination-oracle-strict-encrypt	❌	❌

if you have connectors that successfully published but failed definition generation, follow step 4 here ▶️

[grishick]

/publish connector=connectors/destination-oracle-strict-encrypt run-tests=false

🕑 Publishing the following connectors:
connectors/destination-oracle-strict-encrypt
https://github.com/airbytehq/airbyte/actions/runs/2693855677

Connector	Did it publish?	Were definitions generated?
connectors/destination-oracle-strict-encrypt	✅	❌

if you have connectors that successfully published but failed definition generation, follow step 4 here ▶️