Adding defaults to use if user is invoking algokit project deploy {mainnet|localnet|testnet} and no .env.{network_name} exists. This should not prevent user from deploying with defaults (and in case of testnet|mainnet it will use free public infrastructure - algonode). But the main reason is to reduce noisy amount of .env files in smart contract based algokit templates.
https://github.com/algorandfoundation/algokit-cli/issues/532
Proposed changes
Adding defaults to use if user is invoking algokit project deploy {mainnet|localnet|testnet} and no .env.{network_name} exists. This should not prevent user from deploying with defaults (and in case of testnet|mainnet it will use free public infrastructure - algonode). But the main reason is to reduce noisy amount of .env files in smart contract based algokit templates.