How to best work together with this team while adapting it to make it our own about aws-dataall HOT 3 CLOSED

Hello,
Customers usually fork the awslabs/aws-dataall repository and create their own branch from which they deploy data.all in their AWS accounts. In this way, they can configure their data.all deployment in their custom branch, and receive updates by merging from the main branch.

This works well if you do not diverge to much from the open-source version (main branch). Customers that want to keep close to the main branch just have to change the cdk.json and cdk.contect.json files, which are the config files for the deployment.

However merge conflicts might appear if you start diverging form the open-source version (editing some functionalities, changing naming convention, ...). Here you have two solutions:

• Resolve potential conflicts when merging from the main branch
• Create a pull request to edit the main branch. If your change benefits other users (adding a new functionality for example), then the team will accept the merge and your version will be similar to the main branch again which means easier code merge for you.

If you need new data.all features and want to create them, I suggest that you create an Github Issue first, so that the data.all team is aware of what you are doing. This will help having your code integrated in the main branch.

I hope this answers your question.

from aws-dataall.

I subscribe @louishourcade response.

Here are some additional tips:

• Check the Roadmap project https://github.com/awslabs/aws-dataall/projects/1 for the latest updates on the tasks picked for development.
• Add your Issues to this Project so the team picks them up faster
• Implement gitignore logic on customized files diverging from the open-source (also cdk.json and cdk.context.json)

from aws-dataall.

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

from aws-dataall.