nettashviro
commented
3 years ago Talk to barak and use the manifests here: https://drive.google.com/drive/u/0/folders/1tCQ57aHjrCCXtYkZ5fLzZ6nx_Qsv9jN3
The DOD for this issue is a complete integration with the indexing-services using apis, everything necessary except the UI. This includes:
[] Talking to Barak's team, understanding the steps of the integration which will have to be executed for the integration to succeed, building a scheme for the full integration with api manifest, types and how the info is obtained (The REST API for api-gw, and grpc and rabbit for the inner-integration). (1.5 days) : This will be presented to @Shahar-Y and @Baraks24 for confirmation.
[ ] Make this issue an Epic and link the related issues to it while also listing them below: (total of 6 days)
- [ ] Lorem Ipsum
- [ ] Dolor sit amet
- [ ] Consectetur adipiscing elit
The epic includes all testing necessary for the implementation, and running in helm successfully (It is Barak's team's job to make their services run in our k8s)
Think about all of the use-cases: creating a file, updating metadata/content, sharing with a new person, deleting the file. Barak's team already thought about all of these so it's worth talking with them thoroughly before running to the implementation.
update for the task: We decided to use Mongo stream watcher in order to follow the changes with the help of listener-service. This service does not have an API or functionality that needs to be added to it in the api-gateway.
Talk to barak and use the manifests here: https://drive.google.com/drive/u/0/folders/1tCQ57aHjrCCXtYkZ5fLzZ6nx_Qsv9jN3
The DOD for this issue is a complete integration with the indexing-services using apis, everything necessary except the UI. This includes:
[ ] Talking to Barak's team, understanding the steps of the integration which will have to be executed for the integration to succeed, building a scheme for the full integration with api manifest, types and how the info is obtained (The REST API for api-gw, and grpc and rabbit for the inner-integration). (1.5 days) : This will be presented to @Shahar-Y and @Baraks24 for confirmation.
[ ] Opening the related issues in the related repositories with time estimation (total of 6 work days). (0.5 days)
[ ] Make this issue an Epic and link the related issues to it while also listing them below: (total of 6 days)
The epic includes all testing necessary for the implementation, and running in helm successfully (It is Barak's team's job to make their services run in our k8s)
Think about all of the use-cases: creating a file, updating metadata/content, sharing with a new person, deleting the file. Barak's team already thought about all of these so it's worth talking with them thoroughly before running to the implementation.