Why?

Users expect integration with various Identity Aware Proxies (IAP) that provide authorization. The use of such proxies brings many benefits.

• Management: provide trustworthy integration with identity providers e..g. Google, LDAP, Kerberos, Keycloak, OAuth
• Audibility write additional metadata about the operations performed by users
• Security No need to keep secrets

Summary

The user should be given the chance to set input parameters in the UI when submitting a workflow from a template.

The work done in argoproj/argo#3498 is great, but it only works when (default?) values for the parameters have been set in arguments.parameters.

Instead I suggest both the list of inputs.parameters and arguments.parameters should be consider

Created by Dylan Hughes via monday.com integration. 🎉

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

Problem to solve

The dagit CLI allows command options to be set via environment variables using the DAGIT prefix, implemented with Click's auto_envvar_prefix feature. I would like to be able to do the same with the dagster CLI.

Intended users

• DevOps Engineer

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