You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing dependencies using the Dependency Manager, the subsequent step involves adding the contracts you wish to deploy to the deployments section of your flow.json. This can be approached in a couple of ways:
The process could be automatic, where it is assumed that you likely want to deploy the contracts to the emulator-account, unless specified otherwise through a flag.
Alternatively, the default approach should not be to automatically add the contracts. Instead, there could be an option to use a flag to add them to deployments.
chasefleming
changed the title
Add depedencies from Dependency Manager to a deployment account
Add dependencies from Dependency Manager to a deployment account
Feb 8, 2024
After thinking about it a bit, a better option might actually be an interactive approach. It could ask you on installing/adding if you want to add the contract it finds to deployments, detect the accounts available, and let you select which to add it to. There could also be an option for --skip-deployments if you are running this from a scenario where you'd want to avoid an interactive prompt.
When installing dependencies using the Dependency Manager, the subsequent step involves adding the contracts you wish to deploy to the
deployments
section of yourflow.json
. This can be approached in a couple of ways:emulator-account
, unless specified otherwise through a flag.deployments
.The command could look something like:
flow deps add testnet://35717efbbce11c74.Find --deployment-account=emulator-account
The text was updated successfully, but these errors were encountered: