The issue was fixed in PR 7854 and will be generally available in Argo Workflows 3.4. Therefore we have no intention on maintaining this repository.
When Argo Workflows archives a workflow, the URL changes, and the URL cannot be pre-determined. If you're using tools such as the ci-github-notifier to annotate results onto Github Pull Requests, this change of URL quickly becomes an issue.
The Argo Workflows URL Finder simply locates your workflow by querying the Argo Workflows API and redirects the user to the correct URL.
We pass key information to the container using environment variables.
| Environment Variable | Type | Description |
|---|---|---|
ARGO_URL |
string | (Mandatory): The url to your argo-workflows installation. eg. https://argo-workflows.sendible.com |
ACCESS_TOKEN |
string | (Optional if TOKEN_FILE is set): An Argo Workflows token with permission to query the API. |
TOKEN_FILE |
string | (Optional if ACCESS_TOKEN is set): Path to a file within the container that contains the Argo Workflows access token. Useful for Vault secrets injection or similar. Takes precedence over ACCESS_TOKEN |
The Argo Workflows URL Finder can be deployed anywhere you can deploy a container. However, if you're running Argo Workflows already, you probably use Kubernetes. We have provided a basic example deployment.
For testing purposes, a simple docker run command could be:
docker run \
-e ARGO_URL=https://argo-workflows.sendible.com/ \
-e ACCESS_TOKEN="xxxx" \
-p 8080:8080 \
ghcr.io/sendible-labs/argo-workflows-url-finder:stable
Assuming we have performed the docker run command above and we have a workflow called wonderful-whale in the namespace testing. We would query for its location by going to http://localhost:8080?workflowname=wonderful-whale&namespace=testing.
The user will be redirected to the workflow regardless of whether it's archived or not.