Feature request: replication sub command

[Touhami-viseo]

sfcc-ci Version

2.12.0

NodeJS Version

16.20.2

sfcc-ci Path

N/A

Host OS Details

Ubuntu 22.04.5 LTS

What happened?

This is a feature request.

In order to improve our delivery pipeline we would like to trigger code replications from staging environment to development and production environments. However, currently there is no way to trigger a code or data replication using sfcc-ci.

Being able to trigger replication from our CI would streamline our delivery process, have better reporting (time to delivery, KPIs, etc.) be more efficient, and reduce deployment errors.

I image this new command:

sfcc-ci code:replicate [options] <codeversion> <target>

Where : <codeversion> is the version to replcate. <target> is either development or production.

Thanks in advance.

Relevant log output

N/A

[vercellone]

@Touhami-viseo My Idea on ideaexchange may interest you: Offer a way to programmatically deploy a code version to production. I would appreciate an upvote, FWIW.

In the meantime, I'm resorting to Playwright for .NET driven browser automation.

[aseyfarth]

Not talking down that a direct API would be great, but there are ways already to achieve that control on your DevOps tooling. And no, I am not referring to browser automation.

You can setup code replication via job step, where a replication for the active code version would be executed. And a job is something you could trigger via the CLI.

So the steps would be:

• code deployment to STG (2FA cert)
• code activation
• trigger code replication job

[vercellone]

Perhaps I should have titled my idea Offer a way to programmatically deploy an inactive (or any) code version to production

I did mention the solution you suggested and explained why it is undesirable.

2. There is a job which can be run programmatically to replicate the currently active code in staging to production. Since our staging instance typically has a newer code version active when we want to deploy to production, we would have to first activate the version we want, replicate it, then revert the active version to what it was. This isn't difficult but would almost certainly cause disruption in staging and potentially expose us to other side effects.

[Touhami-viseo]

@Touhami-viseo My Idea on ideaexchange may interest you: Offer a way to programmatically deploy a code version to production. I would appreciate an upvote, FWIW.

I upvoted your suggestion.

Do you know where is the best place to request features from Salesforce?