bloomtech-labs / dep-story-squad-ds-b Goto Github PK

• I'm submitting a ...

  • bug report
  • feature request
  • support request

• Do you want to request a feature or report a bug?

  Feature : adding a database to the deployment image to store vectors for clustering purposes

• What is the current behavior?

  Currently nothing is stored by the Data Science API

• If the current behavior is a bug, please provide the steps to reproduce the behavior. _{NA Not a bug report}

• What is the expected behavior?

  To implement advanced clustering techniques and to assist with returning cluster grouping for RC3-Gamification roadmap goal storage of Principal components and or vector representations of the transcriptions along with the calculated SquadScore will be added on the AWS console and baked in to the existing DS API framework for submitting an upload for transcribing.

• What is the motivation / use case for changing the behavior?

  As Explained above this feature is for advancement on the product roadmap to RC3-Gamification. The use of a Database in the design of the application will increase our efficiency and remove redundant calculations of submissions. Which will reduce the usage of the Google Vision API and other cloud compute resources that are leveraged to transcript and score submissions.

• Please tell us about your environment: _{NA Not a bug report}

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

• I'm submitting a ...

  • bug report
  • feature request
  • support request

• Do you want to request a feature or report a bug?

Bug with Header authorization checking.

• What is the current behavior?
  Currently regardless of the value of the "Authorization" header the user is allowed to interact with any of the endpoints and send and receive data from them.

• If the current behavior is a bug, please provide the steps to reproduce the behavior.
  Any properly formed POST to one of the endpoints will return the expected value from that endpoint.

• What is the expected behavior?

If the value of the "Authorization" header is DS_SECRET_TOKEN the the application works as expected and returns the appropriate data from the endpoints.

if the value of Authorization header is not DS_SECRET_TOKEN then a 403: forbidden error is returned to the user instead of the expected data from the endpoint call.

• What is the motivation / use case for changing the behavior?

Informational Security and compliance with COPPA regulations

• Please tell us about your environment:

  Operating system and current build version: Win, WSL2: 4.4.0-19041-Microsoft #488-Microsoft Mon Sep 01 13:43:00 PST 2020 x86_64 x86_64 x86_64 GNU/Linux

  Output from pip freeze for the following packages:

  on python 3.7.6

  fastapi==0.60.1
  pandas
  numpy
  plotly
  uvicorn==0.11.8
  google-cloud-vision==1.0.0
  textstat==0.6.2
  

  output from command:

  python 3.7.6
python 3.8.2

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

• I'm submitting a ...

  • bug report
  • feature request
  • support request

• Do you want to request a feature or report a bug?
  CI Pipeline from linting to deployment using GitHub actions.

• What is the current behavior?
  Currently there is nothing automated in the development Pipeline from submitting code, merging to main, rebuilding the docker image, pushing the docker image, and redeploying the application on AWS EBS. everything in the flow must be done manually.

• If the current behavior is a bug, please provide the steps to reproduce the behavior.

NA

• What is the expected behavior?

The exspected beharior of this feature would be to automate all of the above steps into a github workflow that takes submitted code on PR open and lints it using black and Flake8, then takes the code and runs unittesting to make sure that the feature wont break the deployment. if the submitted code passes the tests then when the PR is merged the main repo will be build into a docker container and pushed to DockerHub and to the AWS Elastic Beanstalk Service.

• What is the motivation / use case for changing the behavior?
  The main motivation of this feature is to streamline the development pipeline to reduce the repetitive tasks that must be done to deploy after merging to the main branch while also improving the quality of the code that is merged into the main branch.

• Please tell us about your environment:
  NA

• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)