-
Notifications
You must be signed in to change notification settings - Fork 0
Implement CRUD operations for User Service #10
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As for me, it looks more like POC for using firebase in python, than sth about user_service
What these models have in common with our (real) application? Where do we will store avatars, profile description, etc? Password user_service will get already hashed, I didn't see you handled this
@ZhavoronkovN hold on. Let me push new commits first) |
Note: for the tests I have created a separate database in Firebase on my personal account. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks much better, well done!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still ok
Description
These changes affect user service only and include CRUD interface for User Service. It operates with the Firebase Real Time database (No SQL database) via client library.
Plus, I have wrapped user service with docker in order to make a deployment more smoth and painless.
Publisher and subscriber python files the way we communicate with Google Pub/Sub in python.
Database connector provides an CRUD interface for user profile information.
Dockerfile simply copy all scripts in the one directory and run main.py as an entry point for the whole user service application. There are just a few lines of code for now. More will be added later.
Issues
LFND-44 | Implement CRUD operations for User Service
How Has This Been Tested?
In order to test this changes you need to add json credentials to the user service root directory (you can download them from google cloud and firebase).
Checklist: