TF Connect solution #31

Closed
opened 2024-03-21 11:39:56 +00:00 by despiegk · 8 comments
Owner

original story, now 4 months old

  • the developers we used for TF Connect are not able to give us the support we need
  • we have choice to create a new version of TF Connect based on flutter using the codebase we have
  • or we can upgrade the code and make sure flagsmith not needed & we migrate the user data (PKI) to TFChain

update

  • what needs to be done?
  • update story/specs
  • we want to be able to properly manage the full TF Connect and backend
## original story, now 4 months old - the developers we used for TF Connect are not able to give us the support we need - we have choice to create a new version of TF Connect based on flutter using the codebase we have - or we can upgrade the code and make sure flagsmith not needed & we migrate the user data (PKI) to TFChain ## update - what needs to be done? - update story/specs - we want to be able to properly manage the full TF Connect and backend
despiegk added the
Story
label 2024-03-21 11:39:56 +00:00
despiegk added this to the (deleted) project 2024-03-21 11:39:56 +00:00
Member

Identified the core the parts where pkid, flagsmith are used, problem with the migration it will require users to open up their phones to execute it, but should be okayish

Identified the core the parts where pkid, flagsmith are used, problem with the migration it will require users to open up their phones to execute it, but should be okayish
Author
Owner

@thabeta please link to info and give comments

what is deadline, delivery, ...

@thabeta please link to info and give comments what is deadline, delivery, ...
Author
Owner
  • we keep tf connect (for version 3.x)
  • then see with Jimber to migrate their server, redundant & backup -> copy data to TFChain
  • remove flagsmith replace with KVS on TFChain (we already have the data)
  • pkid: replace with KVS on TFChain
  • no civic we use the other KYC provider
- we keep tf connect (for version 3.x) - then see with Jimber to migrate their server, redundant & backup -> copy data to TFChain - remove flagsmith replace with KVS on TFChain (we already have the data) - pkid: replace with KVS on TFChain - no civic we use the other KYC provider
Member

for data migration to be completed and tested on staging by 7th of may

for data migration to be completed and tested on staging by 7th of may
Member
https://github.com/threefoldtech/threefold_connect/issues/597 won't be before 15th of may earliest
despiegk modified the project from (deleted) to tfgrid_3_14 2024-05-22 07:56:24 +00:00
Author
Owner

what is status, what is deliverable for 3.14
would be nice to have KYC possibilities again, which we can rely upon from elsewhere e.g. we sign centrally and we can consult it in other apps to see user has been KYC'ed

if too much work move to 3.15 but make sure we have clean story

what is status, what is deliverable for 3.14 would be nice to have KYC possibilities again, which we can rely upon from elsewhere e.g. we sign centrally and we can consult it in other apps to see user has been KYC'ed if too much work move to 3.15 but make sure we have clean story
Member

this wasn't able to complete due to work on services migration

TODO: redo a new story and include kyc

this wasn't able to complete due to work on services migration TODO: redo a new story and include kyc
thabeta modified the project from tfgrid_3_14 to tfgrid_3_17 2024-06-02 06:21:15 +00:00
despiegk modified the project from tfgrid_3_17 to tfgrid_3_20 2024-07-03 12:54:15 +00:00
despiegk removed this from the tfgrid_3_20 project 2024-07-03 12:54:19 +00:00
thabeta was assigned by despiegk 2024-07-28 07:52:05 +00:00
despiegk added this to the tfgrid_3_17 project 2024-07-28 07:52:08 +00:00
Member

data migration done and have a stable env, i'll close this one in favor of the KYC/T&C ticket #12

data migration done and have a stable env, i'll close this one in favor of the KYC/T&C ticket https://git.ourworld.tf/tfgrid/circle_engineering/issues/12
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: tfgrid/circle_engineering#31
No description provided.