mirror of
https://github.com/empayre/fleet.git
synced 2024-11-06 08:55:24 +00:00
b1945b2128
Closes: https://github.com/fleetdm/confidential/issues/4057 Changes: - Added the contents of the fleet-vulnerability-dashboard repo to ee/vulnerability-dashboard - Added a github workflow to deploy the vulnerability dashboard on Heroku - Added a github workflow to test changes to the vulnerability-dashboard - Updated the website's custom configuration to enable auto-approvals/review requests to files in the ee/vulnerability-dashboard folder
125 lines
6.6 KiB
JavaScript
125 lines
6.6 KiB
JavaScript
/**
|
|
* Default model settings
|
|
* (sails.config.models)
|
|
*
|
|
* Your default, project-wide model settings. Can also be overridden on a
|
|
* per-model basis by setting a top-level properties in the model definition.
|
|
*
|
|
* For details about all available model settings, see:
|
|
* https://sailsjs.com/config/models
|
|
*
|
|
* For more general background on Sails model settings, and how to configure
|
|
* them on a project-wide or per-model basis, see:
|
|
* https://sailsjs.com/docs/concepts/models-and-orm/model-settings
|
|
*/
|
|
|
|
module.exports.models = {
|
|
|
|
|
|
/***************************************************************************
|
|
* *
|
|
* Whether model methods like `.create()` and `.update()` should ignore *
|
|
* (and refuse to persist) unrecognized data-- i.e. properties other than *
|
|
* those explicitly defined by attributes in the model definition. *
|
|
* *
|
|
* To ease future maintenance of your code base, it is usually a good idea *
|
|
* to set this to `true`. *
|
|
* *
|
|
* > Note that `schema: false` is not supported by every database. *
|
|
* > For example, if you are using a SQL database, then relevant models *
|
|
* > are always effectively `schema: true`. And if no `schema` setting is *
|
|
* > provided whatsoever, the behavior is left up to the database adapter. *
|
|
* > *
|
|
* > For more info, see: *
|
|
* > https://sailsjs.com/docs/concepts/orm/model-settings#?schema *
|
|
* *
|
|
***************************************************************************/
|
|
|
|
schema: true,
|
|
|
|
|
|
/***************************************************************************
|
|
* *
|
|
* How and whether Sails will attempt to automatically rebuild the *
|
|
* tables/collections/etc. in your schema. *
|
|
* *
|
|
* > Note that, when running in a production environment, this will be *
|
|
* > automatically set to `migrate: 'safe'`, no matter what you configure *
|
|
* > here. This is a failsafe to prevent Sails from accidentally running *
|
|
* > auto-migrations on your production database. *
|
|
* > *
|
|
* > For more info, see: *
|
|
* > https://sailsjs.com/docs/concepts/orm/model-settings#?migrate *
|
|
* *
|
|
***************************************************************************/
|
|
|
|
migrate: 'alter',
|
|
|
|
|
|
/***************************************************************************
|
|
* *
|
|
* Base attributes that are included in all of your models by default. *
|
|
* By convention, this is your primary key attribute (`id`), as well as two *
|
|
* other timestamp attributes for tracking when records were last created *
|
|
* or updated. *
|
|
* *
|
|
* > For more info, see: *
|
|
* > https://sailsjs.com/docs/concepts/orm/model-settings#?attributes *
|
|
* *
|
|
***************************************************************************/
|
|
|
|
attributes: {
|
|
createdAt: { type: 'number', autoCreatedAt: true, },
|
|
updatedAt: { type: 'number', autoUpdatedAt: true, },
|
|
id: { type: 'number', autoIncrement: true, },
|
|
//--------------------------------------------------------------------------
|
|
// /\ Using MongoDB?
|
|
// || Replace `id` above with this instead:
|
|
//
|
|
// ```
|
|
// id: { type: 'string', columnName: '_id' },
|
|
// ```
|
|
//
|
|
// Plus, don't forget to configure MongoDB as your default datastore:
|
|
// https://sailsjs.com/docs/tutorials/using-mongo-db
|
|
//--------------------------------------------------------------------------
|
|
},
|
|
|
|
|
|
/******************************************************************************
|
|
* *
|
|
* The set of DEKs (data encryption keys) for at-rest encryption. *
|
|
* i.e. when encrypting/decrypting data for attributes with `encrypt: true`. *
|
|
* *
|
|
* > The `default` DEK is used for all new encryptions, but multiple DEKs *
|
|
* > can be configured to allow for key rotation. In production, be sure to *
|
|
* > manage these keys like you would any other sensitive credential. *
|
|
* *
|
|
* > For more info, see: *
|
|
* > https://sailsjs.com/docs/concepts/orm/model-settings#?dataEncryptionKeys *
|
|
* *
|
|
******************************************************************************/
|
|
|
|
dataEncryptionKeys: {
|
|
default: 'VErvj3YDSyWKg4ReQj8BWodHEDaIbvob0+uOvzv4LZY='
|
|
},
|
|
|
|
|
|
/***************************************************************************
|
|
* *
|
|
* Whether or not implicit records for associations should be cleaned up *
|
|
* automatically using the built-in polyfill. This is especially useful *
|
|
* during development with sails-disk. *
|
|
* *
|
|
* Depending on which databases you're using, you may want to disable this *
|
|
* polyfill in your production environment. *
|
|
* *
|
|
* (For production configuration, see `config/env/production.js`.) *
|
|
* *
|
|
***************************************************************************/
|
|
|
|
cascadeOnDestroy: true
|
|
|
|
|
|
};
|