updatecli icon indicating copy to clipboard operation
updatecli copied to clipboard

Feature Request: Using local scm directory

Open olblak opened this issue 2 years ago • 0 comments

Is your feature request related to a problem?

Today we can't contribute a new file and a new Updatecli manifest at the same time in the same pullrequest. The reason is:

When a manifest relies on a git repository, Updatecli clone that repository in a temporary location then do all the changes there instead of doing the change in the local directory.

This is the chicken and the egg problem, We can't test updating something that do not exist yet on the remote repository

This UX experience is annoying because we need first to submit the change and in a second interation submit the Updatecli manifest.

Solution you'd like

I would like that if I run updatecli diff from a git directory then I would like to use that directory instead of the one in "/tmp"

Alternatives you've considered

At the moment, we usually "comment" all annoying scmid such as:

targets:
  default:
    name: Bump my target
    # scmid: default
   kind: yaml
   spec:
     file: data.yaml

Anything else?

Because the file to update doesn't exist yet, it doesn't make sense to run updatecli apply but it could be useful to run updatecli diff to see what would change...

olblak avatar Sep 08 '23 11:09 olblak