Files
zitadel/proto/buf.yaml
Stefan Benz ff6d593922 fix: remove action feature flag and include execution (#9727)
# Which Problems Are Solved

Actions v2 is not a feature flag anymore, include functionality on
executions is not used and json tags of proto messages are handled
incorrectly.

# How the Problems Are Solved

- Remove actions from the feature flags on system and instance level
- Remove include type on executions, only in the API, later maybe in the
handling logic as well
- Use protojson in request and response handling of actions v2

# Additional Changes

- Correct integration tests for request and response handling
- Use json.RawMessage for events, so that the event payload is not
base64 encoded
- Added separate context for async webhook calls, that executions are
not cancelled when called async

# Additional Context

Related to #9759
Closes #9710

---------

Co-authored-by: Livio Spring <livio.a@gmail.com>
(cherry picked from commit b8ba7bd5ba)
2025-04-29 13:05:22 +02:00

43 lines
1.0 KiB
YAML

version: v1
name: buf.build/zitadel/zitadel
deps:
- buf.build/grpc-ecosystem/grpc-gateway
- buf.build/envoyproxy/protoc-gen-validate
- buf.build/googleapis/googleapis
breaking:
use:
- FILE
- FIELD_NO_DELETE_UNLESS_NAME_RESERVED
- FIELD_NO_DELETE_UNLESS_NUMBER_RESERVED
except:
- FIELD_NO_DELETE
ignore_unstable_packages: true
lint:
use:
- MINIMAL
ignore:
- zitadel/action.proto
- zitadel/admin.proto
- zitadel/app.proto
- zitadel/auth_n_key.proto
- zitadel/auth.proto
- zitadel/change.proto
- zitadel/event.proto
- zitadel/feature.proto
- zitadel/idp.proto
- zitadel/instance.proto
- zitadel/management.proto
- zitadel/member.proto
- zitadel/message.proto
- zitadel/metadata.proto
- zitadel/object.proto
- zitadel/options.proto
- zitadel/org.proto
- zitadel/policy.proto
- zitadel/project.proto
- zitadel/quota.proto
- zitadel/settings.proto
- zitadel/system.proto
- zitadel/text.proto
- zitadel/user.proto
- zitadel/v1.proto