# Force Override Upgrade Validation

**URL:** <https://forum.openzeppelin.com/t/force-override-upgrade-validation/5368>\
**Category:** Upgrades\
**Created:** [January 11, 2021, 2:55pm UTC](https://forum.openzeppelin.com/t/force-override-upgrade-validation/5368 "2021-01-11T14:55:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bh2smith](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/bh2smith/32/4043_2.png) [@bh2smith](https://forum.openzeppelin.com/u/bh2smith)\
**Post date:** [January 11, 2021, 2:55pm UTC](https://forum.openzeppelin.com/t/force-override-upgrade-validation/5368/1 "2021-01-11T14:55:47Z")

</div>

When attempting to use openzeppelin-upgrades we are able to override only a particular subset of unsafe actions (namely `unsafeAllowCustomTypes` and `unsafeAllowLinkedLibraries`). However in some cases, one may want to override things like “Use of delegatecall is not allowed” (e.g. when delegate calls are only used to read contract storage).

Would it be within the realm of possibility to include a manual override for all validations, or simply a `forceSkipValidation` feature?

---

<div class="post-metadata">

**Author:** ![frangio](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/frangio/32/15251_2.png) [@frangio](https://forum.openzeppelin.com/u/frangio)\
**Post date:** [January 12, 2021, 12:21am UTC](https://forum.openzeppelin.com/t/force-override-upgrade-validation/5368/2 "2021-01-12T00:21:31Z")

</div>

Hi @bh2smith, this is definitely possible and I think it’s a good idea. I’ve created an issue:

> <https://github.com/OpenZeppelin/openzeppelin-upgrades/issues/280>
>
> Requested in https://forum.openzeppelin.com/t/force-override-upgrade-validation/5368:
> When attempting to use openzeppelin-upgrades we are able to override only a particular subset of unsafe actions (namely unsafeAllowCustomTypes...

---

<div class="post-metadata">

**Author:** ![abcoathup](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/abcoathup/32/415_2.png) [@abcoathup](https://forum.openzeppelin.com/u/abcoathup)\
**Post date:** [January 12, 2021, 4:26am UTC](https://forum.openzeppelin.com/t/force-override-upgrade-validation/5368/3 "2021-01-12T04:26:14Z")

</div>

Hi @bh2smith,

Welcome to the community 👋

---

<div class="post-metadata">

**Author:** ![bh2smith](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/bh2smith/32/4043_2.png) [@bh2smith](https://forum.openzeppelin.com/u/bh2smith)\
**Post date:** [January 12, 2021, 8:27am UTC](https://forum.openzeppelin.com/t/force-override-upgrade-validation/5368/4 "2021-01-12T08:27:35Z")

</div>

Hey there @abcoathup! Thanks for the warm welcome. Very glad to be here.

On a similar note to the issue I have posted here, I created a PR regarding providing your own deployment function to the `deployProxy` method in hardhat-upgrades.

> <https://github.com/OpenZeppelin/openzeppelin-upgrades/pull/273>

I was hoping to provide a working example of these feature, but ran into this roadblock along the way. Once we have this manual override, it will be much easier for me to ensure the content of the PR is working as expected.

Cheers!