This the parent configuration object and holds all the underlying configuration object types. An instance of this object holds all the config necessary to

  1. Interactive session with Union backend

  2. Some parts are required for Serialization, for example Platform Config is not required

  3. Runtime of a task

entrypoint_settings: EntrypointSettings object for use with Spark tasks. If supplied, this will be

used when serializing Spark tasks, which need to know the path to the flytekit file, inside the container.
Automatically constructs the Config Object. The order of precedence is as follows
  1. first try to find any env vars that match the config vars specified in the FLYTE_CONFIG format.

  2. If not found in environment then values ar read from the config file

  3. If not found in the file, then the default values are used.


config_file (str | ConfigFile | None) – file path to read the config from, if not specified default locations are searched



Return type:


flytekit.configuration.Config.for_endpoint(endpoint, insecure=False, data_config=None, config_file=None)#

Creates an automatic config for the given endpoint and uses the config_file or environment variable for default. Refer to to understand the default bootstrap behavior.

data_config can be used to configure how data is downloaded or uploaded to a specific Blob storage like S3 / GCS etc. But, for permissions to a specific backend just use Cloud providers reqcommendation. If using fsspec, then refer to fsspec documentation :param endpoint: -> Endpoint where Flyte admin is available :param insecure: -> if the connection should be insecure, default is secure (SSL ON) :param data_config: -> Data config, if using specialized connection params like minio etc :param config_file: -> Optional config file in the flytekit config format. :return: Config

  • endpoint (str)

  • insecure (bool)

  • data_config (DataConfig | None)

  • config_file (str | ConfigFile)

Return type:



Constructs a new Config object specifically to connect to deployment-deployment-sandbox. If you are using a hosted Sandbox like environment, then you may need to use port-forward or ingress urls :return: Config

Return type: