We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On https://docs.openzeppelin.com/upgrades-plugins/1.x/defender-deploy and https://docs.openzeppelin.com/upgrades-plugins/1.x/foundry-defender, clarify that the API key and secret referenced in the following statement is for the Production or Test Deploy Environment that was configured in Defender:
Set the following environment variables in your .env file at your project root, using your Team API key and secret from OpenZeppelin Defender:
Consider linking to https://docs.openzeppelin.com/defender/v2/tutorial/deploy#environment_setup
See https://forum.openzeppelin.com/t/add-support-to-create-proposals-through-the-openzeppelin-defender-within-a-foundry-project/38754/8
The text was updated successfully, but these errors were encountered:
No branches or pull requests
On https://docs.openzeppelin.com/upgrades-plugins/1.x/defender-deploy and https://docs.openzeppelin.com/upgrades-plugins/1.x/foundry-defender, clarify that the API key and secret referenced in the following statement is for the Production or Test Deploy Environment that was configured in Defender:
Consider linking to https://docs.openzeppelin.com/defender/v2/tutorial/deploy#environment_setup
See https://forum.openzeppelin.com/t/add-support-to-create-proposals-through-the-openzeppelin-defender-within-a-foundry-project/38754/8
The text was updated successfully, but these errors were encountered: