#Refocus api token database updates

[pallavi2209]

New Model: Token

Columns:

• name - allowNull: false, validate using db/constants.nameRegex, use db/constants.fieldlen.normalName for field length
• token - allowNull: false, string
• isDeleted - dataTypes.BIGINT, defaultValue: 0, allowNull: false
• isDisabled - follow the same pattern we use for "isDeleted" so a record is considered "disabled" when this field has a non-zero value

Indexes:

• unique on lower(name)+createdBy+isDeleted

Associations:

• createdBy association to User

Scopes:

• default scope should exclude the token field and should order by name ascending

Hooks:

• beforeCreate - reuse db/helpers/userUtils.hashPassword to store the encrypted version of the token

Permissions:

• Profile checks will be in the API layer, not the DB layer

[coveralls]

Coverage increased (+0.02%) to 83.975% when pulling a5ac0eb on token-db-updates into c8424e5 on master.

[shriramshankar]

Do we need a name field ?

[iamigo]

If a user has multiple tokens, the name field makes it possible to identify a particular token one might wish to disable or delete

[shriramshankar]

@iamigo @pallavi2209 Any thoughts on having a default values for all the data types? We might be able to get ride of the responsify function at one point of time.

[iamigo]

Shriram can you create a spike for team to discuss this? (But let's not let it hold up this particular PR.)

[iamigo]

will approve after fixing reference to lens/lenses

[iamigo]

?

[coveralls]

Coverage increased (+0.02%) to 83.975% when pulling 652ed73 on token-db-updates into 4df2b8f on master.

[pallavi2209]

@iamigo @shriramshankar updated the PR.

[coveralls]

Coverage increased (+0.02%) to 83.975% when pulling 7d69ea0 on token-db-updates into 2337cc5 on master.

[coveralls]

Coverage increased (+0.04%) to 82.208% when pulling 6ce4698 on token-db-updates into a73a4aa on master.

[coveralls]

Coverage increased (+0.04%) to 82.208% when pulling c819876 on token-db-updates into ca2ac27 on master.