Composer install broken: no extension able to load the configuration for "fixity_algorithm"

[seth-shaw-unlv]

I was setting up riprap on our mock-production box today. When I ran 'composer install' I was given the following error block:

Executing script cache:clear [KO]
 [KO]
Script cache:clear returned with error code 1
!!  
!!  In FileLoader.php line 166:
!!                                                                                 
!!    There is no extension able to load the configuration for "fixity_algorithm"  
!!     (in /opt/riprap/config/services.yaml). Looked for namespace "fixity_algori  
!!    thm", found "framework", "monolog", "doctrine_cache", "doctrine", "doctrine  
!!    _migrations", "maker", "security", "web_server", "doctrine_fixtures", "swif  
!!    tmailer" in /opt/riprap/config/services.yaml (which is loaded in resource "  
!!    /opt/riprap/config/services.yaml").                                          
!!                                                                                 
!!  
!!  In YamlFileLoader.php line 666:
!!                                                                                 
!!    There is no extension able to load the configuration for "fixity_algorithm"  
!!     (in /opt/riprap/config/services.yaml). Looked for namespace "fixity_algori  
!!    thm", found "framework", "monolog", "doctrine_cache", "doctrine", "doctrine  
!!    _migrations", "maker", "security", "web_server", "doctrine_fixtures", "swif  
!!    tmailer"                                                                     
!!                                                                                 
!!  
!!  
Script @auto-scripts was called via post-install-cmd

My config/services.yaml file has the line fixity_algorithm: sha256 which worked before on stock claw-playbook installs, so I'm not sure what happened this time. It did complain at the beginning of the composer install that The lock file is not up to date with the latest changes in composer.json. Might this be related to the recent lock-file issue (#35)?

[seth-shaw-unlv]

Nevermind. I was half-following my old steps from back in January and had copied the islandora sample config over config/services.yaml. 🤦‍♂️

I restored the services.yaml to the default and composer install worked fine.