search

Adobe-Consulting-Services / acs-aem-commons

http://adobe-consulting-services.github.io/acs-aem-commons/
Apache License 2.0
453 stars 600 forks source link

Do not start services on AEMaaCS instances if they are not working there #2282

Closed joerghoh closed 4 years ago

joerghoh commented 4 years ago

In the documentation a number of features are listed already as "do not use them when you are deploying on AEM as a CloudService".

Right now this is not technically enforced, but with the RequireAem feature (see https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/b391b2455bb1aac018183ae4b76794379ebb8a59/bundle/src/main/java/com/adobe/acs/commons/util/RequireAem.java) it can be enforced quite easily.

Right now these features are tagged as "do not run within AEMaaCS":

bulk-workflow-manager
ensure-oak-index
healthchecks/smtp
healthchecks/status-emailer
healthchecks
json-event-logger
versioned-clientlibs
workflow-processes/assets-rendition-matter
workflow-processes/assets-watermark-process
workflow-processes/brand-portal
file-fetcher
mcp-tools/asset-ingestion/asset-ingestor
mcp-tools/asset-ingestion
mcp-tools/asset-ingestion/s3-asset-ingestor
mcp-tools/asset-ingestion/url-asset-ingestor
mcp-tools/refresh-folder-thumbnails
redirect-map-manager
remote-assets

(I have extracted this list from the official documentation)

joerghoh commented 4 years ago

see #2285

joerghoh commented 4 years ago

2285 has been merged, closing this one.