Hello,

Currently, you can define a new connection/variable in several ways.

• Metabase
• Environment variable
• Secret backend

However, only the connections defined with the Metabase are visible from the Web UI. This is surprising among users because a natural way to check connection/variable configuration is to use the Web UI, which may not show complete information.
I would be happy if

Summary

When an environment variable is populated from a secret, the server UI shows undefined for its value. This is highly confusing because the user's first reaction is that the secret value isn't being correctly passed. This messaging could be improved by showing secret or hidden or something to that effect, to indicate that the value does exist, but is not displayed.

Description

From community slack: https://prefect-community.slack.com/archives/CL09KU1K7/p1599551263372600

From that slack comment:

_I am trying to run a DbtShellTask with a dynamic set of dbt_kwargs that are defined at run time. The task works when I define the dbt_kwargs in the task initialization, but not when they are provided at runtime.

Looks like the dbt_kwargs needs an em

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

https://www.loom.com/share/41acf7e9e0224073b50266e89cf16aa8

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