Skip to content

Fix docs for SCRIPT_RUN stage #4736

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ffjlabo merged 1 commit into from
Dec 25, 2023
Merged

Fix docs for SCRIPT_RUN stage #4736

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions ...n/docs-dev/user-guide/managing-application/customizing-deployment/script-run.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ description: >

`SCRIPT_RUN` stage is one stage in the pipeline and you can execute any commands.

> Note: This feature is at the alpha status and only available for application of kind AWS Lambda.
> Note: This feature is at the alpha status.

## How to configure SCRIPT_RUN stage

Expand Down Expand Up @@ -49,7 +49,7 @@ spec:
sleep 10
```

![](/images/custom-sync.png)
![](/images/script-run.png)

Note:
1. You can use `SCRIPT_RUN` stage with any current supporting application kind.
Expand All @@ -61,4 +61,7 @@ Note:
- Build your own container image based on `ghcr.io/pipe-cd/piped` image.
- Manually update your running piped container (not recommended).

# When to rollback

Even if a rollback occurs, the command will not be executed again.
In the near future, we are considering the ability to run this command also on rollback.