A small potential improvement... We could use method chain on Project instead? then you could do something like Init().WithComposeSources(...).WithEvns(...).WithSkaffold(...).WithUI(...).

@marcinc ... To clarify:

Do you mean instead of passing opts to Init(). And, creating extra methods on Project to perform the wiring?

But how would you know which method (.WithComposeSources(...) or .WithEvns) to call?

yeh, that's what I meant. Current implementation is correct, just thought that method chain could be slightly nicer. To your question, I think you'd know which method to chain the same way you know it now.. an excertp:

	return kev.InitProjectWithOptions(wd,
		kev.WithComposeSources(files),
		kev.WithEnvs(envs),
		kev.WithSkaffold(skaffold))

# this would become

	return kev.InitProject(wd).WithComposeSources(files).WithEnvs(envs).WithSkaffold(skaffold)

Tbh, I would rather leave it as is.

Otherwise, you would need to:
-> kev.InitProject(wd) to return a runner object.
-> Configure using With... methods.

... And you also then:
-> have to Run() the runner.
-> and do the other things that InitProjectWithOptions is doing for you.

as said, it's good as is. If chaining brings extra complexity then that's fine.

with deployment environments at ... -> with deployment environment profiles at ...

makes sense for now I guess. Later we could have it managed centrally / or locally when needed by chaining .Wait(time.Seconds * 1) or similar. Could be done in a follow up PR as discussed.

This is outdated.