Summary

• #2443
• Support ${status.startedAt} and ${status.finishedAt} as substitutable variables in links.
  • Links just support ${metadata.name}, ${metadata.namespace} variables now.

Use Cases

• For example, administrators can provide a link to Log Dashboard within the time window.

Hello!

I've found an issue here:In order to deploy your flow to Kubernetes the flow is required to have a Docker Storage with the image pushed to a registry that your Kubernetes cluster has access to.

Page reference: https://docs.prefect.io/orchestration/tutorial/k8s.html

Is it in fact true that a flow deployed to Kubernetes EKS can't use s3 storage? If so, an explicit affirmation of th

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.

Issue

16 files has some sort of Sugar Pro references in code as comments.
Those should be removed

Steps to Reproduce

Try the search with BEGIN: pro
https://github.com/salesagility/SuiteCRM/search?q

rn we get:
Exception: Can not import module <ipython-input-19-f2a127b099dd> from path /Users/max/dev/dagster/python_modules/dagster/<ipython-input-19-f2a127b099dd>, unable to load spec.

Had the branch ancestry:

branch-1
  branch-2-bug-fix
    branch-3

All three branches had an open PR. branch-2-bug-fix‘s PR was a duplicate of a fix that someone else had already put in and merged at the same time. I closed the PR on branch-2-bug-fix and ran git town kill on that branch.

I was expecting it to change the base branch of branch-3‘s PR but instead it closed it