Bulk updating gem source
The rest of the code collects errors, and redirects the user back to the form action.
Sometimes, it is more convenient to be able to update nodes using non-original clients.
This document shows how to set the permissions on node objects to allow any client the ability to update any node.
After these changes are made, you will be able to delete the client for a given node, then run chef-client on the node and the new client will able to update the node's data object on the Chef Server.
The way to avoid this problem is to update Ruby Gems… Unfortunately, this was not in my local repository.
That being said, even by running the validations, it ran in about 25 seconds, which is the second fastest time I was able to get.
In this article, we relied upon our not-null database constraints along with a unique index, and then we used the ability to insert multiple records with a single SQL query.
This is how Rails handles saving a model by default…
unless of course we wrap it in our own transaction, a single one that we can use for all 50,000 records.