Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MGDCTRS-1037: Auto increment connector revision #426

Merged
merged 2 commits into from
Nov 9, 2022
Merged

Conversation

lburgazzoli
Copy link
Contributor

@lburgazzoli lburgazzoli commented Oct 4, 2022

This PR introduces:

  • automatic connector revision management based on changes in the transitive dependencies or in the connector type definition
  • build container images only for connector that have changed
  • use cos-manifests as a storage for the catalog definition (this may be a temporary solution)
  • no need to store generated files in the repository

The flow to update cos-manifests and then build the catalog images and trigger the re-deployment of the dev env has still to be implemented but requires this PR to be merged first

@lburgazzoli
Copy link
Contributor Author

@rinaldodev @hdamarcelo @valdar I've re-opened the PR as a branch of the main repo to get some integration test running against reals services (salesforce, azure, etc)

@heiko-braun
Copy link

@lburgazzoli @rinaldodev Close or rebase?

@lburgazzoli
Copy link
Contributor Author

will rebase

@lburgazzoli lburgazzoli marked this pull request as draft November 7, 2022 15:06
@lburgazzoli lburgazzoli force-pushed the MGDCTRS-1037 branch 4 times, most recently from de5ea46 to 271bca0 Compare November 9, 2022 10:39
@lburgazzoli lburgazzoli marked this pull request as ready for review November 9, 2022 21:38
@lburgazzoli lburgazzoli merged commit ea6451f into main Nov 9, 2022
@lburgazzoli lburgazzoli deleted the MGDCTRS-1037 branch November 9, 2022 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants