DVO-4886 - gha secret issues

[TarasDz]

This changes should fix the issue with secretes:

[Invalid workflow file: .github/workflows/deploy-api.yml#L19](https://github.com/voltrondata/substrait-fiddle/actions/runs/7183899727/workflow)
The workflow is not valid. .github/workflows/deploy-api.yml (Line: 19, Col: 9): Unrecognized named-value: 'secrets'. Located at position 36 within expression: github.ref == 'refs/heads/main' && secrets.DEPLOY_SSH_KEY && secrets.DEPLOY_HOST_DNS && secrets.DEPLOY_USERNAME && secrets.DEPLOY_TARGET_DIR

Also added path so if there will be any changes in .github/workflow/** to trigger the jobs

[voltrondatabot]

Task linked: DVO-4886 Investigate issue with GitHub actions secrets

[amaldonadomat]

I want to make sure that the workflow works before merging this, so please provide some proof that it works. And also agree with amol and assignUser on their comments

[TarasDz]

Hello @amol- @assignUser @amaldonadomat

The recent PR aims to facilitate the deployment of substrait-fiddle using docker-compose. This will be achieved by implementing a new workflow that will be triggered if changes are pushed to the main branch or if any of the specified paths are modified. These paths include client/**, api/**, github/workflows/deploy-api-client.yml, and docker-compose.yaml

In order to run docker-compose on a remote host, we will use SSH-Compose. This will allow as to manage and configure the remote host efficiently

To deploy substrait-fiddle on the host, certain prerequisites must be met. These include pre-configuring some packages on the host and having a deploy user to run docker. The PR is in labs repo, we configured the instance to create with security groups that open ports 22, 80, and 443. This will ensure that the necessary connections are available

I was able to create the instance using pulumi with pre-configured packages, then I run GHA on my fork to deploy substrait-fiddle on new host:

currently it's running on instance IP: http://18.116.28.34/
we still working on DNS transfer, and once it will be finished we will update the IaC code

Please review this PR and let us know if you have any questions or comments

[amaldonadomat]

Thanks @TarasDz
This looks great, much easier to deploy with the docker compose

[assignUser]

Wow what a cool way to deploy, thanks! I left some minor best practice security suggestions.