eddeca2942
This removes some DeprecationWarnings in history-v1 The update should be safe: ``` 3.0.0 / 2018-11-20 Ensure config array items and objects are sealed @fgheorghe This required a major version bump in case someone relied on the ability to mutate non-sealed data. 2.0.0 / 2018-07-26 Potential for backward incompatibility requiring a major version bump. Safe to upgrade to major version 2 if you're using a recent NodeJS version and you're not trying to mutate config arrays. Added array immutability - jacobemerick Removed Node V.4 support ``` https://github.com/node-config/node-config/blob/master/History.md GitOrigin-RevId: 8384247d1ad2cd659703b4ba50edf7212076dcf3
Database migrations
The history service uses knex to manage PostgreSQL migrations.
To create a new migrations, run:
npx knex migrate:make migration_name
To apply migrations, run:
npx knex migrate:latest
For more information, consult the knex migrations guide.
Global blobs
Global blobs are blobs that are shared between projects. The list of global blobs is stored in the projectHistoryGlobalBlobs Mongo collection and is read when the service starts. Changing the list of global blobs needs to be done carefully.
Adding a blob to the global blobs list
If we identify a blob that appears in many projects, we might want to move that blob to the global blobs list.
- Add a record for the blob to the projectHistoryGlobalBlobs collection.
- Restart the history service.
- Delete any corresponding project blobs.
Removing a blob from the global blobs list
Removing a blob from the global blobs list is trickier. As soon as the global blob is made unavailable, every project that needs the blob will have to get its own copy. To avoid disruptions, follow these steps:
-
In the projectHistoryGlobalBlobs collection, set the
demotedproperty tofalseon the global blob to remove. This will make the history system write new instances of this blob to project blobs, but still read from the global blob. -
Restart the history service.
-
Copy the blob to all projects that need it.
-
Remove the blob from the projectHistoryGlobalBlobs collection.
-
Restart the history service.