Onboard Intake(2/3): introduce Intake

[devanshcache]

Description

Intake is composed of three components:

• Intake Runners: dedicated, isolated runtime data ingestion environment
• Intakes: a specific data stream or topic within an Intake Runner
• Intake Users: provides secure access credentials for your applications to connect to your Intake.

Intake runner has already been merged reference (#952) this PR is continuation of the one of two components of Intake (ticket)

Checklist

• Issue was linked above
• Code format was applied: make fmt
• Examples were added / adjusted (see e.g. here)
• Docs are up-to-date: make generate-docs (will be checked by CI)
• Unit tests got implemented or updated
• Unit tests are passing: make test (will be checked by CI)
• No linter issues: make lint (will be checked by CI)

[rubenhoenle]

Just for my understanding: What is an "intake"? Is it kind of an instance (like it is for managed databases)?

Because I would maybe suggest something like stackit beta intake instance create then...

[rubenhoenle]

Please use our new testutil funcs testutil.TestParseInput or testutil.TestParseInputWithAdditionalFlags to save us and yourself all the boilerplate code here.

See #1033 for reference.

stackit-cli/internal/pkg/testutils/testutils.go

Lines 14 to 22 in fb6cfca

	// TestParseInput centralizes the logic to test a combination of inputs (arguments, flags) for a cobra command
	func TestParseInput[T any](t *testing.T, cmdFactory func(*types.CmdParams) *cobra.Command, parseInputFunc func(*print.Printer, *cobra.Command, []string) (T, error), expectedModel T, argValues []string, flagValues map[string]string, isValid bool) {
	TestParseInputWithAdditionalFlags(t, cmdFactory, parseInputFunc, expectedModel, argValues, flagValues, map[string][]string{}, isValid)
	}
	// TestParseInputWithAdditionalFlags centralizes the logic to test a combination of inputs (arguments, flags) for a cobra command.
	// It allows to pass multiple instances of a single flag to the cobra command using the `additionalFlagValues` parameter.
	func TestParseInputWithAdditionalFlags[T any](t *testing.T, cmdFactory func(*types.CmdParams) *cobra.Command, parseInputFunc func(*print.Printer, *cobra.Command, []string) (T, error), expectedModel T, argValues []string, flagValues map[string]string, additionalFlagValues map[string][]string, isValid bool) {
	p := print.NewPrinter()

[rubenhoenle]

Or is there any reason why you're not using it? Then please tell me, so we can fix potential issues 😅

[rubenhoenle]

same here, please use the testutil func

[rubenhoenle]

same here, please use the testutil func

[rubenhoenle]

same here, please use the testutil func

[rubenhoenle]

Why are you using the testutils.TestParseInput func here but not for your other implementations? 😅

This is the way, please use it everywhere.

[rubenhoenle]

Suggested change

	prompt := fmt.Sprintf("Are you sure you want to create an Intake for project %q?", projectLabel)
	prompt := fmt.Sprintf("Are you sure you want to create an Intake instance for project %q?", projectLabel)

In case it's an instance, I would phrase it like this

[rubenhoenle]

Suggested change

	p.Printer.Info("%s stackit Intake instance %s \n", operationState, model.IntakeId)
	p.Printer.Outputf("%s stackit Intake instance %s \n", operationState, model.IntakeId)

p.Printer.Info would log to stderr, p.Printer.Outputf logs to stdout. I guess you want log to stdout here 😅

[rubenhoenle]

@devanshcache please note: All of this also applies to #1126