Re-introduce command steps

[c-pius]

Description

The previous implementation included command steps. We need to consider adding steps again.

Reasons

Better feedback to the end user and more robustness for the e2e tests (rely on the step output and not plain logs).

Attachments

[github-actions]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

[github-actions]

This issue has been automatically closed due to the lack of recent activity.
/lifecycle rotten

[github-actions]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

[github-actions]

This issue has been automatically closed due to the lack of recent activity.
/lifecycle rotten

[github-actions]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

[c-pius]

The "step" implementation in the create command is basic logging, e.g.:

modulectl/internal/service/create/create.go

Line 197 in 1f95f05

opts.Out.Write("- Creating component archive\n")

In Kyma CLI, this was more sophisticated, see:

• new step: https://github.com/kyma-project/cli/blob/2.20.2/cmd/kyma/alpha/create/module/module.go#L259
  • end with success: https://github.com/kyma-project/cli/blob/2.20.2/cmd/kyma/alpha/create/module/module.go#L273
  • end with failure: https://github.com/kyma-project/cli/blob/2.20.2/cmd/kyma/alpha/create/module/module.go#L264
• https://github.com/kyma-project/cli/blob/2.20.2/internal/cli/command.go#L19-L23
• https://github.com/kyma-project/cli/blob/2.20.2/pkg/step/step.go
• https://github.com/kyma-project/cli/blob/2.20.2/pkg/step/spinner.go