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.

Sign up for GitHub

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

docs: DR for azure distrubution deprecation #1612

Merged
merged 4 commits into from
Oct 10, 2024
Merged

docs: DR for azure distrubution deprecation #1612

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
56a38da
docs: DR for azure distrubution deprecation
ndr-brt Oct 7, 2024
c568029
rephrase
ndr-brt Oct 8, 2024
d1977f5
pr remark
ndr-brt Oct 9, 2024
466c261
dependencies
ndr-brt Oct 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions docs/development/decision-records/2024-10-07-azure-distribution/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# Refactor of the Release Workflow

## Decision

We will stop to provide an azure flavoured distribution of the connector.
ndr-brt marked this conversation as resolved.
Show resolved Hide resolved

## Rationale

Two reasons are pushing toward this decision:
- Tractus-X Connector is a reference implementation for Catena-X: so nothing should stop anybody to build and use their
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like the point of this first item should not be towards the freedom dataspace participants have to create their own distribution, because this is true since the beginning of the project. What is different at this point, IMO, is how easy it is to create and release a new distribution using the existing one as reference.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This point was meant to tell the community that we don't "have to" maintain such distribution because our goal is not to provide different distributions for different needs, but to provide one (the reference one) and everyone should feel free to customize it according to their needs.
I can rephrase a little, but that's one of the reasons why

Copy link
Contributor

@rafaelmag110 rafaelmag110 Oct 8, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understood what you meant. Just don't want this to be seen as a "you are free to develop your own stuff if you need it" but rather a "it's not our intention to do it and we made it as easy as possible for you to do it".
Looks better now, in my opinion.

own Connector (also without using EDC), so there are no reasons for us to maintain more than one distribution.
- Tractus-X is an open source software and we should focus on a distribution that involves OSS services.

## Approach

We will deprecate, 0.8.0:
- `tractusx-connector-azure-vault` helm chart
- `edc-controlplane-postgresql-azure-vault` docker image
- `edc-dataplane-postgresql-azure-vault` docker image

We will stop publishing them from version 0.9.0 on.
Loading