feat: provision a teamer from a received application

This commit is contained in:
fromme committed 2026-09-25 14:36:24 +02:00
1 parent d5f4b12f0a
commit b530679658
23 files changed
+2433 -148

No files matched your search

+5
View File
@@ -13,3 +13,8 @@ flagception:
myep_login:
default: false
env: FEATURE_MYEP_LOGIN
# Provisioning writes to the production CRM and cannot be rehearsed: the teamer selection
# is only changeable there. Ships off.
application_form_teamer_provisioning:
default: false
env: FEATURE_APPLICATION_FORM_TEAMER_PROVISIONING
+7
View File
@@ -169,6 +169,13 @@ services:
bpn_api_port: '%env(APP_BPN_PORT)%'
debug: '%env(bool:APP_BPN_DEBUG)%'
App\Service\Teamer\TeamerProvisioner:
arguments:
$logger: '@monolog.logger.bpn'
# The same selection the login reads a teamer's role from - this is the one place that
# writes it, so it must be the same id.
$teamerSelectionId: '%bpn_crm_id_teamer%'
App\BusProNet\ResponseParser:
arguments:
$options: