Skip to content

Conversation

@tkotthakota-adobe
Copy link
Collaborator

@tkotthakota-adobe tkotthakota-adobe commented Jun 11, 2025

Create Spacecat task processor lambda as SQS consumer to receive messages (type, payload) via defined SQS queue. Based on the type, right task handler is invoked to fulfill the task. Slack context can be passed in the message to get the task response after completion.

https://jira.corp.adobe.com/browse/SITES-32832
https://wiki.corp.adobe.com/display/AEMSites/Spacecat+Onboard+Automation

Test result on slack channel:

image

@github-actions
Copy link

github-actions bot commented Jun 13, 2025

This PR will trigger a patch release when merged.

Copy link
Collaborator

@rpapani rpapani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please incorporate the provided feedback, rest looks good 👍

@tkotthakota-adobe
Copy link
Collaborator Author

@rpapani addressed review comments.

  1. Under the secret name: /helix-deploy/spacecat-services/task-manager/latest below keys are added on dev. Same need to be added in prod:
    IMS_ORG_TENANT_ID_MAPPINGS
    SLACK_BOT_TOKEN
    SLACK_SIGNING_SECRET
    SLACK_TOKEN_WORKSPACE_INTERNAL
    SLACK_OPS_CHANNEL_WORKSPACE_INTERNAL
    SLACK_TOKEN_ADOBE_INTERNAL

  2. We also need to add lambda trigger on prod env.

@tkotthakota-adobe tkotthakota-adobe merged commit fda7068 into main Jul 8, 2025
7 checks passed
@tkotthakota-adobe tkotthakota-adobe deleted the SITES-30108-step-functions-poc branch July 8, 2025 21:37
solaris007 pushed a commit that referenced this pull request Jul 8, 2025
# 1.0.0 (2025-07-08)

### Features

* Spacecat task processor lambda ([#1](#1)) ([fda7068](fda7068))
@solaris007
Copy link
Member

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants