GoogleContainerTools / GoogleContainerTools/skaffold

Changes to skaffold.env don't trigger re-deploy

Open
#9,793 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Go
Stars
15.9k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
10

Description

When running via `skaffold dev`, a change to `skaffold.yaml` will trigger a redeployment of the application without rebuilding the container.

A change to `skaffold.env` will be treated like any source file. If it's added to the container via a COPY, then a change will trigger a restart PLUS a Docker Build. Otherwise it's ignored, and changes don't trigger a redeployment.

Expected: `skaffold.env` should be watched by default, and changes to variable values should result in release deployments.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.