feat: builds namespace

[vladfrangu]

Screenshots incoming, tests too (probably will rely on cucumber tests)

Closes part of the #619 epic

builds ls

builds info

builds info --json

builds create --actor=id

builds create --actor=id --tag=string | multiple versions tagged the same way

builds create --actor=id --tag=non-existent

THIS NEEDS A REVIEW FROM @netmilk!!

builds create --actor=id --tag=string --version=string

[netmilk]

@vladfrangu I've manually validated all the functionality provided by this PR, and it works as expected. Thank you! I'd wait with merging for the Cucumber spec, though.

Just one improvement proposal:
Shouldn't the $ apify build create always attach to the log the same way apify push does? If so, I'd add --detach flag to exit 0 right after successfully creating a build.

[netmilk]

I've just noticed the $ apify builld log subcommand, which is implemented and isn't mentioned in this PR. Because of that I've missed it initially.

$ apify build log for a running build should attach terminal to the build session and keep printing until the build is finished.

[vladfrangu]

Thats what it does @netmilk, re apify build log 👀

Related to apify builds create, do we.. want to also attach the logs automatically? Can we get that documented on notion too (also maybe make it opt-in, or bring in the --wait-for-finish flag from other cmds)

[netmilk]

Understood. Perfect. Thank you for explaining it to me.

What about $ apify builds create --log and let's keep attach / dettach words for the streaming?

[vladfrangu]

So what would --log do? Attach the log stream on command run? And wdym by attach / detach for streaming?

[netmilk]

@vladfrangu, I'm sorry for the ambiguity. Yes, it would connect apify build log to the newly created build.

By "streaming" I mean connecting to platform live events during a run. Run, Dataset, KVS, RQ Creation, Status messages, push-data, set-value as briefly mentioned in the internal spec.

[B4nan]

looks good, but we need at least the cucumber tests before merging

[barjin]

Just a few copy nits I noticed when skimming the PR... the screenshots look bomb!

Btw do we communicate that "Builds" are a platform-only feature anywhere? As a new user, I would definitely assume that I can build the Actors locally with CLI as well (maybe more of a question for @netmilk , sorry if this has been discussed somewhere before).

[janbuchar]

I noticed that your run methods tend to be very long, which makes them hard to read. Other than that and a few minor comments/questions, I think this is good to go.

[B4nan]

as discussed on slack, i would love to see more e2e test assertions, i get that it might be too complicated to deal with it properly, but at least some lower effort asserts (e.g. to detect one line we know should be there) would be great