Manage MarketplaceApplicationCatalog entity instances. Handle basic CRUD operations.
Handle the creation of a new marketplace vendor catalog based on the creation of a vendor elsewhere.
This vendor catalog will also be associated to marketplace application(s) as determined by MarketplaceDiscoverer.
This is a component invoked by TenantVendorNotificationHandler to determine which marketplace applications to associate an automatically-created vendor catalog to.
(since 1.7.6) By default, it will look for active marketplace applications in the datastore.
If exactly one candidate marketplace is found, then it will be returned as eligible for assignment.
If zero or multiple candidate marketplaces are found, then nothing will be returned as eligible for assignment.
This is important to ensure deterministic behavior in multi-marketplace scenarios.
(prior to 1.7.6) By default, it will choose the first active marketplace application it can find.
Fragment repository for handling specialized persistence behavior for applications.
Fragment repository override to handle specialized persistence behavior for JpaTenantCatalog instances.
Fragment repository for handling specialized persistence behavior for marketplace application catalog relationships.
At the time of this writing, there’s no sandboxable entities in this service. If a sandboxable entity is introduced in this service, the following configurations should be added:
spring:
cloud:
stream:
bindings:
persistenceOutput:
triggeredJobEventInputPurgeSandbox:
group: tenant-purge-sandbox
destination: triggeredJobEvent
broadleaf:
transitionrequest:
enabled: true
changesummary:
notification:
active: true
tracking:
sandbox:
purge:
enabled: trueSee Sandboxing In Detail for more details.
|
Note
|
These configurations typically only affect the
Granular Deployment model. For Min and Balanced deployements, these configurations are likely already added at the flexpackage-level configuration.
|