feat: add manual layer sync

[LucasMrqes]

[Alan-pad]

@LucasMrqes If you create a TerraformRun directly that would be easier I think and should still work, you'd have to make sure there's no other TerraformRun running but apart from that it should be straightforward to implement plan/apply buttons

[LucasMrqes]

@LucasMrqes If you create a TerraformRun directly that would be easier I think and should still work, you'd have to make sure there's no other TerraformRun running but apart from that it should be straightforward to implement plan/apply buttons

I think using the controller to generate the run is a better way. I tried to create the run resource with the server and encountered the following issues:

• The status of the layer is not updated, thus making the layer status + run history incoherent and messing with how the server finds the last run in its /layers path. (unless we duplicate this logic in the server as well)
• Not using the controller to generate runs makes it complicated to debug using the manual sync Button, as the run creation logic is somewhat duplicated and the button would bypass the ususal flow of creating run/pods with Burrito
• Overall, the required logic is way more complicated

wdyt @Alan-pad ?

[Alan-pad]

I think we can adapt the controller logic so the new runs are picked up

[LucasMrqes]

Implementing this feature with a tfrun creation requires us to rework the logic of the layer controller. This is something that we plan to do, but since this feature is requested a lot by Burrito users, we will merge this as is and work on a rework on future versions of Burrito.

[corrieriluca]

Great feature! 👏

[corrieriluca]

Removing the annotation right away is causing another reconciliation right?
Does the layer end in a NoSyncScheduled status just a few seconds later? Does it impact the Server API in its SyncLayerHandler ?

[LucasMrqes]

The layer controller creates a run, and the run controller locks the layer related to a this new run until the run succeeds or fails. Since the layer is locked during the whole duration of the run, this should not cause any issue.