How to manage the .openzeppelin file from a location other than the project root directory

I'm part of an organization that runs private networks and use upgradeable contracts. Our smart contract dev environment uses hardhat, and the openzeppelin-upgrades plugin is great for checking for storage conflicts and for deployment/upgrades.
I was wondering if there are examples available of how to create, read, and update the .openzeppelin file from a location other than the hardhat project root directory?

Hi @bold, the .openzeppelin directory location isn't customizable at the moment. Can you please open a GitHub issue and provide some details on your expected use case?

As a workaround, you could run your Hardhat command from another directory (and use relative or absolute paths to locate your Hardhat scripts), so the .openzeppelin subdirectory under that path would be used instead. If you have existing deployments, make sure to move the existing .openzeppelin folder to be under the root of that path.

1 Like

Hey @ericglau, I opened up this issue: