Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

hello all, I have
```
remote = FlyteRemote(
    config=Config.for_endpoint(endpoint='localhost:30080'),
    default_project="flytesnacks",
    default_domain="development",
)

flyte_wf = remote.fetch_workflow(
    name="flyte.workflows.extract_flyte.extract_drs_data",
    project="flytesnacks",
    domain='development',
)```

maybe set `insecure=True` :thinking_face: thats in platform config

```class PlatformConfig(object):
    """
    This object contains the settings to talk to a Flyte backend (the DNS location of your Admin server basically).

    :param endpoint: DNS for Flyte backend
    :param insecure: Whether to use SSL
    :param insecure_skip_verify: Whether to skip SSL certificate verification
    :param console_endpoint: endpoint for console if different from Flyte backend
    :param command: This command is executed to return a token using an external process
    :param client_id: This is the public identifier for the app which handles authorization for a Flyte deployment.
      More details here: <https://www.oauth.com/oauth2-servers/client-registration/client-id-secret/>.
    :param client_credentials_secret: Used for service auth, which is automatically called during pyflyte. This will
      allow the Flyte engine to read the password directly from the environment variable. Note that this is
      less secure! Please only use this if mounting the secret as a file is impossible
    :param scopes: List of scopes to request. This is only applicable to the client credentials flow
    :param auth_mode: The OAuth mode to use. Defaults to pkce flow
    :param ca_cert_file_path: [optional] str Root Cert to be loaded and used to verify admin
    """

    endpoint: str = "localhost:30080"
    insecure: bool = False
    insecure_skip_verify: bool = False```