V2 operator/agent should set custom user-agent for Pulumi operations

[rquitales]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

We should update our agent server code to also use a custom user-agent string for Pulumi auto api operations. This was done in v1 of the operator. Ref:

pulumi-kubernetes-operator/pkg/controller/stack/stack_controller.go

Lines 1619 to 1628 in 2ca7753

	func (sess *reconcileStackSession) UpdateStack(ctx context.Context, targets []string) (shared.StackUpdateStatus, shared.Permalink, *auto.UpResult, error) {
	writer := sess.logger.LogWriterDebug("Pulumi Update")
	defer contract.IgnoreClose(writer)
	opts := []optup.Option{optup.ProgressStreams(writer), optup.UserAgent(execAgent)}
	if targets != nil {
	opts = append(opts, optup.Target(targets))
	}
	result, err := sess.autoStack.Up(ctx, opts...)

[EronWright]

@rquitales I believe this is already done, for example:

pulumi-kubernetes-operator/agent/pkg/server/server.go

Line 513 in 17d8dc8

optup.UserAgent(UserAgent),

[EronWright]

I suppose we should add the version info to make the user agent be equivalent to v1:

execAgent               = fmt.Sprintf("pulumi-kubernetes-operator/%s", version.Version)

[cleverguy25]

Added to epic #586