[public-api] Add AuthProviderService service

[AlexTugarev]

Description

Depends on #19041, which depends on #19017

This PR adds and implements public-api service for AuthProviders

Summary generated by Copilot

🤖 Generated by Copilot at 55bd7e7

This pull request adds the AuthProviderService to the experimental API, which is a service for managing authentication providers. It generates the code for the service using different protocols and plugins, such as gRPC, Connect, and protoc-gen-go-grpc. It also adds the proto file that defines the service and its messages and enums.

Related Issue(s)

Fixes #

How to test

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - at-authprovider-api
• 🔗 URL - at-authprovider-api.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - at-authprovider_api-gha.19687
• 🗒️ Logs - GCP Logs Explorer

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[akosyakov]

we don't require both? it is rather at least one of them should be present

[akosyakov]

I used following pattern here:

gitpod/components/server/src/api/organization-service-api.ts

Lines 244 to 265 in c33b555

	const update: Partial<ProtocolOrganizationSettings> = {};
	if (typeof req.workspaceSharingDisabled === "boolean") {
	update.workspaceSharingDisabled = req.workspaceSharingDisabled;
	}
	const hasDefaultWorkspaceImage = typeof req.defaultWorkspaceImage === "string";
	const resetDefaultWorkspaceImage = req.resetMask?.paths.includes("defaultWorkspaceImage");
	if (hasDefaultWorkspaceImage && resetDefaultWorkspaceImage) {
	throw new ConnectError(
	"defaultWorkspaceImage cannot be set and reset at the same time",
	Code.InvalidArgument,
	);
	}
	if (resetDefaultWorkspaceImage) {
	update.defaultWorkspaceImage = null;
	} else if (hasDefaultWorkspaceImage) {
	update.defaultWorkspaceImage = req.defaultWorkspaceImage;
	}
	if (Object.keys(update).length === 0) {
	throw new ConnectError("nothing to update", Code.InvalidArgument);
	}

not sure whether we want to align

[AlexTugarev]

This would mean, we need to change the Dashboard part and retest the behavior. I'd rather avoid.

[akosyakov]

• We don't build API for one client (dashboard).
• If dashboard already provides both values it should not be an issue anyway?

[AlexTugarev]

Ah, now I got you.

we don't require both? it is rather at least one of them should be present

wasn't clear from that.

So, even if Dashboard is always sending the tuple, we may allow for adjusting a single attribute here as well, right? We can change that. Just the focus wasn't on changing existing behavior for the migration phase.

[AlexTugarev]

resolved in fc3be82

[akosyakov]

pre approved, but please to align on contract, and unnecessary checks before mergin 🙏

[AlexTugarev]

@akosyakov, I've address the comments and added tests.

Going to test in preview and proceed afterwards.

[AlexTugarev]

/unhold