-
Notifications
You must be signed in to change notification settings - Fork 5
Remove Hard SES dependency #5
Copy link
Copy link
Closed
Labels
effort/mDaysDaysenhancementNew feature or requestNew feature or requestimpact/manyAffects most usersAffects most userspriority/p2Backlog-worthyBacklog-worthyseverity/mediumModerate harmModerate harmtriagedItem has been triagedItem has been triagedtype/featNew capabilityNew capabilityurgency/this-sprintWithin the current sprintWithin the current sprint
Metadata
Metadata
Assignees
Labels
effort/mDaysDaysenhancementNew feature or requestNew feature or requestimpact/manyAffects most usersAffects most userspriority/p2Backlog-worthyBacklog-worthyseverity/mediumModerate harmModerate harmtriagedItem has been triagedItem has been triagedtype/featNew capabilityNew capabilityurgency/this-sprintWithin the current sprintWithin the current sprint
Currently when a new user signs up they have to reset password via email making an SES dependency a must. This email reset and broadly SES dependency should be optional especially if customer does not want to get notification etc. and we currently have a path for customers to insert secrets into the env during deployment for database setup so we should use that as well as to support setting the password & Username at deploy time for the frontend.