github
/
portainer
mirror of https://github.com/portainer/portainer
1
0
Fork 0
Code Issues Releases Wiki Activity

fix(autoupdate): update tooltips in edge stack gitops update [BE-12177] (#1084)

develop
Oscar Zhou 2025-08-23 10:56:04 +12:00 committed by GitHub
parent ec0e98a64b
commit 2ce8788487
1 changed files with 17 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
app/react/portainer/gitops/AutoUpdateFieldset/AutoUpdateSettings.tsx
View File

@ -77,7 +77,7 @@ export function AutoUpdateSettings({
checked={value.ForcePullImage || false}
label="Re-pull image"
labelClass="col-sm-3 col-lg-2"
tooltip="If enabled, then when redeploy is triggered via the webhook or polling, if there's a newer image with the tag that you've specified (e.g. changeable development builds), it's pulled and redeployed. If you haven't specified a tag, or have specified 'latest' as the tag, then the image with the tag 'latest' is pulled and redeployed."
tooltip="If enabled, then when redeploy is triggered via the webhook or polling, if there's a newer image with the tag that you've specified (e.g. changeable development builds), it's pulled and redeployed. If you haven't specified a tag, or have specified 'latest' as the tag, then the image with the tag 'latest' is pulled and redeployed. With relative path enabled, it also redeploys when mounted files (not just the compose file) change."
onChange={(value) => onChange({ ForcePullImage: value })}
/>
</div>
@ -107,7 +107,22 @@ export function AutoUpdateSettings({
the cluster being overwritten.
</p>
</>
) : undefined
) : (
<p>
If enabled, then when redeploy is triggered via the webhook or
polling, the stack behavior depends on the stack type:
<br />
<strong>Regular stacks:</strong> Redeploy whenever triggered,
without checking for docker-compose file changes
<br />
<strong>Edge stacks:</strong> Redeploy only when the
docker-compose file in the Git repository has changed. Commits
that change unrelated files or mounted files (via relative paths)
do not trigger redeployment. Currently, this option does not
change the redeployment behavior, and it remains a temporary
solution until a more complete behavior is added later.
</p>
)
}
/>
</>