feat: added Contentstack's destination-action.

[hanoak20]

Added Contentstack's Destination Action.

Description:
Added an action called "customAttributesSync" to sync custom attributes, computed attributes, and audience into Contentstack's Personalization. All of these syncs work on 'identify' events.

[joe-ayoub-segment]

Hi @hanoak20 thanks for raising this PR.

I'm out of office until 16-May and will review the PR then.

If you have an urgent query please email partner-support@segment.com

Kind regards,
Joe

[tcgilbert]

You'll need to correct the Custom Attributes Sync description. Adding the requested extendRequest is optional, but I believe you'll find that it cleans up your code a good deal.

One thing you'll need to add eventually are some unit tests. But considering you primarily want this deployed to test in private, I'll go ahead and mark this ready for release so this will be included in the next deployment.

The next deploy is scheduled on Tuesday.

[joe-ayoub-segment]

Can we do this in the standard way instead of accessing the rawData unnecessarily?
We only allow use of rawData as a workaround as it breaks a platform standard convention and builds up technical debt.

perform: async (request, {payoad}) => {

Simply add a field called traits.

{
   traits: {
       type: "object",
       default: {"@path": "$.traits"}, 
       label: "User traits",
       description: "User Profile traits to send to Contentstack",
       required: true
    }
}

Then the code for customTraitsOfSegment will be a lot simpler:

   const attributesToCreate = Object.keys(payload.traits).filter(
      (trait: string) => !personalizeAttributesData.includes(trait)
    )

[joe-ayoub-segment]

userId should also be a field.

{
   userId: {
       type: "string",
       default: {"@path": "$.userId"}, 
       label: "User ID",
       description: "ID for the user",
       required: false
    }
}

you will then access it like this:

'x-cs-eclipse-user-uid': payload.userId ?? ''

[joe-ayoub-segment]

Suggested change

	json: rawData?.traits,
	json: payload.traits,

[joe-ayoub-segment]

This shouldn't be needed if you use regular fields for accessing data.

[joe-ayoub-segment]

Suggested change

	'This action is used to sync custom attributes to your contentstack experience, and is only compatible with Identify events.',
	'Sync Custom Attributes to your Contentstack Experience.',

[sankartn]

Hi @joe-ayoub-segment Just to let you know that, the description was like this only even previously. We updated as per Thomas's comments only.

[joe-ayoub-segment]

hi @hanoak20 thanks again for raising this PR.

I'm just back from PTO and noticed that there are some things that we do need to change before we deploy this code.

I've provided suggestions. These changes are super simple but will reduce the potential for technical debt on our platform.

Kind regards,
Joe

cc @tcgilbert

[joe-ayoub-segment]

hi @hanoak20 - PR deployed. Please confirm the change is good !