https://github.com/parodos-dev/workflow-software-templates/issues/24

Two issues:

1- The webhook cannot reach the server: avoid to create the webhook (always for now, with a user option in the future) and have a CD application to monitor the workflow repo and trigger the pipeline instead

2- the deploy GH action cannot reach the server: as a first option, document a procedure to manually install the same resources. An automated procedure can use a Backstage driven approach instead, like use the argocd:create-resources action doc