Skip to content

Support for multiple deployments in one comment #411

@dezsibalint

Description

@dezsibalint

Details

Hello

I would like to ask if it is possible to replace context.payload.comment.body with a specific comment body that is passed through the workflow call.

The reason I’m asking is that I want to support multiple deployments from a single comment. The repository I’m working on contains many different ArgoCD-managed apps (spread across 10+ clusters).

The way we currently use .deploy is like this:

.deploy app1-enva

where app1 is the application and enva is the cluster where we want to deploy it.

I forked the repo about 2 months ago and made it work by building a matrix from the different .deploy commands and then running each sequentially. However, the branch-deploy workflow wanted to use the whole comment, e.g.:

.deploy app1-enva .deploy app2-envb

So I made some changes in the code and replaced context.payload.comment.body with a specific COMMENT_BODY passed from the matrix (always the one currently deploying). This worked.

Now, I’ve been asked if there’s a way to merge this change back into the original repo so we don’t need to maintain a separate fork.

So my question is: Is it possible to merge my changes that replace context.payload.comment.body with a specific comment body that gets passed in through the workflow call? Or it would break too many things for other users?

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested or the issue is a question

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions