Feature: Protect existing workflow files from accidental overwrites. #3407
Conversation
The `func config ci` command previously overwrote existing workflow
files silently, risking loss of user customizations.
Now the command checks if a workflow file exists before writing and
returns an error unless the `--force` flag is specified. This gives
users explicit control over when to replace their existing workflows.
Additionally, remote builds now use a distinct default workflow name
("Remote Func Deploy") to avoid conflicts.
Issue knative#3256
Signed-off-by: Stanislav Jakuschevskij <sjakusch@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: twoGiants The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
knative-prow-robot
added
the
needs-rebase
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
knative-prow
bot
added
the
size/L
|
@twoGiants: The following test failed, say
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
2 participants
Changes
--forceflag tofunc config cito prevent accidental overwrites of existing workflow filesfunc config cicommand/kind enhancement
Relates to #3256
Release Note