#1570 Support URLs in API Keys Pull request opened by EngHabu TL;DR Adds support for URLs within API Keys to remove the need for a config file entirely. Type ☐ Bug Fix ☑︎ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description This PR builds on the work in #1569. It adds another key in the encoded API Key (endpoint) to make it possible to get rid of the config file entirely for simple use-cases.

echo '{"client_id":"abc","client_secret":"def","url":"<http://my-endpoint.com|my-endpoint.com>"}' | base64

FLYTE_CREDENTIALS_API_KEY=eyJjbGllbnRfaWQiOiJhYmMiLCJjbGllbnRfc2VjcmV0IjoiZGVmIiwidXJsIjoibXktZW5kcG9pbnQuY29tIn0K pyflyte run --remote my_wp.py wf

Minor fixes: ☑︎ Pass

verify

options (for SSL) to other authentication providers not just PKCE ☑︎ If an APIKey is set as an env var and no config file exist, do not assume it's sandbox cluster Tracking Issue https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit GitHub Actions: lint ✅ 29 other checks have passed 29/30 successful checks