After investigation of the updates needed to support search from the old VT repo to the new one @palmajano has identified the following:
Currently a GitHub action variable is used to identify the tenant and 2 GH actions to publish or unpublish documents use this variable to invoke the lambda functions to ingest and delete documents into OpenSearch. Due to the migration to the AEM repo for VT where all tenants will go live in the same repo, we need to send this variable in the event that triggers the actions.
This event is sent by Adobe and invoked by an unknown whenever a page is published or unpublished. Thus we need to include the tenant in this event to be readable by the GitHub actions. The event configuration is tailored to our solution.
In order to complete the successful migration to the new AEM repository for Volvo Trucks the following task are to be performed:
[x] Identify the source of the event
[x] Include in there the tenant
[x] Update the GH actions to read the tenant from the event instead of the variable
[ ] Configure the agent that triggers the event to work with the new setup
verareljic
commented
5 days ago
Related to #691
After investigation of the updates needed to support search from the old VT repo to the new one @palmajano has identified the following: Currently a GitHub action variable is used to identify the tenant and 2 GH actions to publish or unpublish documents use this variable to invoke the lambda functions to ingest and delete documents into OpenSearch. Due to the migration to the AEM repo for VT where all tenants will go live in the same repo, we need to send this variable in the event that triggers the actions. This event is sent by Adobe and invoked by an unknown whenever a page is published or unpublished. Thus we need to include the tenant in this event to be readable by the GitHub actions. The event configuration is tailored to our solution.
In order to complete the successful migration to the new AEM repository for Volvo Trucks the following task are to be performed: