feat: deploy command

[aorumbayev]

Proposed changes

• Introducing deploy command with the following behaviour:
• • By default grabs deploy configurations from hardcoded settings that rely on algonode for testnet/betanet/mainnet and localnet values for sandbox
• • By default assumes that network specific deployment command is specified in algokit.toml file otherwise expects it to be passed via the argument
• • If deployment is being performed to mainnet it will explicitly warn user whether he wants to continue otherwise user can pass --prod flag to skip the warning prompt
• • Deployer mnemonic is required to be passed explicitly via masked input interactively or directly as an argument (useful in CI), docs are to be improved to explicitly make it clear that dispenser is optional while deployer is required if deployment is being done to non localnet networks
• • As discussed and agreed with @achidlow @Loedn and @daniel-makerx , we are going ahead with support for .env.{any_network_name_or_default_networks} approach. That way user still has an option to pick our default localnet|betanet|testnet|mainnet algonode configs OR he defines {any_network_name_or_default_networks} in algokit.toml (or passed directly via flag) AND has a .env.[any_network_name_or_default_networks] to define network configurations

Examples

algokit.toml

[algokit]
min_version = "version_goes_her"

[deploy.localnet]
command = "command_goes_here"

[deploy.testnet]
command = "command_goes here"

OR user can have any custom name basically
[deploy.{any_network_name_or_default_networks}]
command = "command_goes_here"
and so on...

.env.[any_network_name_or_default_networks] file with expectations (same content as current .env content on beaker templates)

# Sandbox
ALGOD_TOKEN=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
ALGOD_SERVER=http://localhost
ALGOD_PORT=4001
INDEXER_TOKEN=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
INDEXER_SERVER=http://localhost
INDEXER_PORT=8980

User can also supply a single .env file without network name prefix, in this case algokit will load that if no env network prefixed file is available. This is useful for cases when deployments are always done to a single network.

Example commands:

algokit deploy {any_network_name_or_default_networks} 
algokit deploy {any_network_name_or_default_networks} --ci --prod 
algokit deploy localnet --custom-deploy command "echo HelloWorld" 

TODO

• Unit/Snapshot tests
• Documentation
• Propagating changes to beaker prod template (env file has to be updated as well as algokit toml file

[aorumbayev]

@inaie-makerx @negar-abbasi tagging you for extra visibility so you are aware in case it overlaps with your items in any way. This will also involve some breaking changes on the beaker template mainly .env files and other configs would need to be placed at the root

[aorumbayev]

@achidlow @daniel-makerx pushed next batch of tweaks, still need some more unit tests to be added but the approach is now refined as agreed with Adam

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
src/algokit
__init__.py	15	7	53%	6–13, 17–24, 32–34
__main__.py	2	2	0%	1–3
src/algokit/cli
completions.py	105	2	98%	80, 95
deploy.py	55	4	93%	34–36, 78
doctor.py	48	3	94%	142–144
generate.py	30	1	97%	49
goal.py	30	1	97%	42
init.py	190	16	92%	264–265, 315, 318–320, 331, 375, 401, 441, 450–452, 455–460, 473
localnet.py	91	3	97%	157, 178–179
src/algokit/core
bootstrap.py	161	24	85%	103–104, 126, 149, 214, 217, 223–237, 246–251
conf.py	54	8	85%	10, 24, 28, 36, 38, 71–73
deploy.py	59	10	83%	60–63, 72–73, 77, 82, 89–91
doctor.py	65	7	89%	67–69, 92–94, 134
log_handlers.py	68	7	90%	50–51, 63, 112–116, 125
proc.py	45	1	98%	98
sandbox.py	150	15	90%	100–107, 118, 226, 242, 257–259, 275
typed_client_generation.py	80	5	94%	55–57, 70, 75
version_prompt.py	73	8	89%	27–28, 40, 59–62, 80, 109
TOTAL	1485	124	92%

Tests	Skipped	Failures	Errors	Time
232	0 💤	0 ❌	0 🔥	16.946s ⏱️