feat: api v2beta to api v2 protos (#8343)

# Which Problems Are Solved

The go linter can't limit the checks to the diff in
https://github.com/zitadel/zitadel/pull/8283 because it's too large

# How the Problems Are Solved

The protos from https://github.com/zitadel/zitadel/pull/8283 are merged
separately

# Additional Context

Contributes to #7236

---------

Co-authored-by: Elio Bischof <elio@zitadel.com>
This commit is contained in:
Stefan Benz
2024-07-26 12:28:28 +02:00
committed by GitHub
parent 57428a1281
commit bc16962aac
57 changed files with 6690 additions and 291 deletions

View File

@@ -5,7 +5,7 @@ module.exports = {
type: "category",
label: "Get Started",
collapsed: false,
link: { type: "doc", id: "guides/start/quickstart" },
link: {type: "doc", id: "guides/start/quickstart"},
items: [
"guides/start/quickstart",
{
@@ -52,7 +52,7 @@ module.exports = {
{
type: "category",
label: "Examples & SDKs",
link: { type: "doc", id: "sdk-examples/introduction" },
link: {type: "doc", id: "sdk-examples/introduction"},
items: [
"sdk-examples/introduction",
"sdk-examples/angular",
@@ -232,7 +232,7 @@ module.exports = {
"guides/integrate/login/oidc/logout",
],
},
"guides/integrate/login/saml",
"guides/integrate/login/saml",
],
},
{
@@ -548,7 +548,7 @@ module.exports = {
items: [
{
type: "category",
label: "V1 (General Available)",
label: "V1 (Generally Available)",
collapsed: false,
link: {
type: "generated-index",
@@ -612,7 +612,7 @@ module.exports = {
},
{
type: "category",
label: "V2 (Beta)",
label: "V2 (Generally Available)",
collapsed: false,
link: {
type: "doc",
@@ -621,71 +621,61 @@ module.exports = {
items: [
{
type: "category",
label: "User Lifecycle (Beta)",
label: "User Lifecycle",
link: {
type: "generated-index",
title: "User Service API (Beta)",
slug: "/apis/resources/user_service",
title: "User Service API",
slug: "/apis/resources/user_service_v2",
description:
"This API is intended to manage users in a ZITADEL instance.\n" +
"\n" +
"This project is in beta state. It can AND will continue breaking until the services provide the same functionality as the current login.",
"This API is intended to manage users in a ZITADEL instance.\n"
},
items: require("./docs/apis/resources/user_service/sidebar.ts"),
items: require("./docs/apis/resources/user_service_v2/sidebar.ts"),
},
{
type: "category",
label: "Session Lifecycle (Beta)",
label: "Session Lifecycle",
link: {
type: "generated-index",
title: "Session Service API (Beta)",
slug: "/apis/resources/session_service",
title: "Session Service API",
slug: "/apis/resources/session_service_v2",
description:
"This API is intended to manage sessions in a ZITADEL instance.\n" +
"\n" +
"This project is in beta state. It can AND will continue breaking until the services provide the same functionality as the current login.",
"This API is intended to manage sessions in a ZITADEL instance.\n"
},
items: require("./docs/apis/resources/session_service/sidebar.ts"),
items: require("./docs/apis/resources/session_service_v2/sidebar.ts"),
},
{
type: "category",
label: "OIDC Lifecycle (Beta)",
label: "OIDC Lifecycle",
link: {
type: "generated-index",
title: "OIDC Service API (Beta)",
slug: "/apis/resources/oidc_service",
title: "OIDC Service API",
slug: "/apis/resources/oidc_service_v2",
description:
"Get OIDC Auth Request details and create callback URLs.\n" +
"\n" +
"This project is in beta state. It can AND will continue breaking until the services provide the same functionality as the current login.",
"Get OIDC Auth Request details and create callback URLs.\n"
},
items: require("./docs/apis/resources/oidc_service/sidebar.ts"),
items: require("./docs/apis/resources/oidc_service_v2/sidebar.ts"),
},
{
type: "category",
label: "Settings Lifecycle (Beta)",
label: "Settings Lifecycle",
link: {
type: "generated-index",
title: "Settings Service API (Beta)",
slug: "/apis/resources/settings_service",
title: "Settings Service API",
slug: "/apis/resources/settings_service_v2",
description:
"This API is intended to manage settings in a ZITADEL instance.\n" +
"\n" +
"This project is in beta state. It can AND will continue to break until the services provide the same functionality as the current login.",
"This API is intended to manage settings in a ZITADEL instance.\n"
},
items: require("./docs/apis/resources/settings_service/sidebar.ts"),
items: require("./docs/apis/resources/settings_service_v2/sidebar.ts"),
},
{
type: "category",
label: "Feature Lifecycle (Beta)",
label: "Feature Lifecycle",
link: {
type: "generated-index",
title: "Feature Service API (Beta)",
slug: "/apis/resources/feature_service",
title: "Feature Service API",
slug: "/apis/resources/feature_service/v2",
description:
'This API is intended to manage features for ZITADEL. Feature settings that are available on multiple "levels", such as instance and organization. The higher level instance acts as a default for the lower level. When a feature is set on multiple levels, the lower level takes precedence. Features can be experimental where ZITADEL will assume a sane default, such as disabled. When over time confidence in such a feature grows, ZITADEL can default to enabling the feature. As a final step we might choose to always enable a feature and remove the setting from this API, reserving the proto field number. Such removal is not considered a breaking change. Setting a removed field will effectively result in a no-op.\n' +
"\n" +
"This project is in beta state. It can AND will continue breaking until a stable version is released.",
'This API is intended to manage features for ZITADEL. Feature settings that are available on multiple "levels", such as instance and organization. The higher level instance acts as a default for the lower level. When a feature is set on multiple levels, the lower level takes precedence. Features can be experimental where ZITADEL will assume a sane default, such as disabled. When over time confidence in such a feature grows, ZITADEL can default to enabling the feature. As a final step we might choose to always enable a feature and remove the setting from this API, reserving the proto field number. Such removal is not considered a breaking change. Setting a removed field will effectively result in a no-op.\n'
},
items: require("./docs/apis/resources/feature_service_v2/sidebar.ts"),
},