update gitSecret feature to handle git.Export

[arsiesys]

Since the following commit, we do not call the Clone function anymore. As a result, the git-secret feature do not work anymore, the apply is done before doing the reveal of the secrets.

6eabb29#diff-ba9f11ecc3497d9993b933fdc2bd61e5,

I am giving the gitSecret option value to the daemon object.. I did not find a better way to do it :(.

[stefanprodan]

@arsiesys the tests are failing:

git/export_test.go:32:28: not enough arguments in call to repo.Export

[squaremo]

I am giving the gitSecret option value to the daemon object.. I did not find a better way to do it :(.

Could it be an option for the Repo, and called as part of repo.go#workingClone, perhaps? If that's possible, I would much prefer it to passing a boolean argument through.

[arsiesys]

I am giving the gitSecret option value to the daemon object.. I did not find a better way to do it :(.

Could it be an option for the Repo, and called as part of repo.go#workingClone, perhaps? If that's possible, I would much prefer it to passing a boolean argument through.

Hello! I just made some tests and sadly, I need to do the git secret reveal after the checkout, it can't be done right after the workingClone cause this one is going to be with master (before the checkout).

I i think, I could eventually, move the call of the secretReveal to the Export function after the checkout call instead of doing it inside the checkout function.

[hiddeco]

@squaremo I performed some CPR on the PR (:recycle: :fish:) and gave Export a dedicated SecretUnseal method so the boolean doesn't have to be passed around everywhere. PTAL.

[squaremo]

This is a neatly cut Gordian knot ⚔️