Closed wackazong closed 4 months ago
Describe the bug near deploy asks a security question whether to overwrite an existing contract also if --force true is used.
near deploy
--force true
To Reproduce near deploy account new.wasm --initFunction init --initArgs '{"some": "args"}' --force true
near deploy account new.wasm --initFunction init --initArgs '{"some": "args"}' --force true
Expected behavior The new wasm should be directly deployed.
Additional context Workaround is to do this echo y | near deploy account new.wasm --initFunction init --initArgs '{"some": "args"}'
echo y | near deploy account new.wasm --initFunction init --initArgs '{"some": "args"}'
should be fixed in latest release (4.0.8) please ping me back if not.
4.0.8
Describe the bug
near deploy
asks a security question whether to overwrite an existing contract also if--force true
is used.To Reproduce
near deploy account new.wasm --initFunction init --initArgs '{"some": "args"}' --force true
Expected behavior The new wasm should be directly deployed.
Additional context Workaround is to do this
echo y | near deploy account new.wasm --initFunction init --initArgs '{"some": "args"}'