Ë ÿ\jg7ãóà—dZddlmZddlmZddlmZddlmZddl m Z ddl m Z ddl mZdd lmZdd lmZdd lmZmZmZmZmZGd „d «ZGd„d«ZGd„d«ZGd„d«Zy)zv This submodule contains factory/configuration methods for integrating the SDK with services other than LaunchDarkly. é)Ú CacheConfig)ÚCachingStoreWrapper)Ú_ConsulFeatureStoreCore©Ú_DynamoDBBigSegmentStore)Ú_DynamoDBFeatureStoreCore©Ú_FileDataSource©Ú_RedisBigSegmentStore)Ú_RedisFeatureStoreCore)ÚBigSegmentStore)ÚAnyÚDictÚListÚMappingÚOptionalcój—eZdZdZ dZeddddej«fdede dede ded e f d „«Z y) ÚConsulzWProvides factory methods for integrations between the LaunchDarkly SDK and Consul. Ú launchdarklyNÚhostÚportÚprefixÚ consul_optsÚcachingÚreturncó6—t||||«}t||«S)aECreates a Consul-backed implementation of :class:`ldclient.interfaces.FeatureStore`. For more details about how and why you can use a persistent feature store, see the `SDK reference guide `_. To use this method, you must first install the ``python-consul`` package. Then, put the object returned by this method into the ``feature_store`` property of your client configuration (:class:`ldclient.config.Config`). :: from ldclient.integrations import Consul store = Consul.new_feature_store() config = Config(feature_store=store) :param host: hostname of the Consul server (uses ``localhost`` if omitted) :param port: port of the Consul server (uses 8500 if omitted) :param prefix: a namespace prefix to be prepended to all Consul keys :param consul_opts: optional parameters for configuring the Consul client, if you need to set any of them besides host and port, as defined in the `python-consul API `_ :param caching: specifies whether local caching should be enabled and if so, sets the cache properties; defaults to :func:`ldclient.feature_store.CacheConfig.default()` )rr)rrrrrÚcores úH/root/env/lib/python3.12/site-packages/ldclient/integrations/__init__.pyÚnew_feature_storezConsul.new_feature_stores!€ô8' t¨T°6¸;ÓGˆÜ" 4¨Ó1Ð1ó) Ú__name__Ú __module__Ú __qualname__Ú__doc__ÚDEFAULT_PREFIXÚ staticmethodrÚdefaultÚstrÚintÚdictrr ©r!rrrsu„ñðAØ#€NàØ$(Ø$(Ø&*Ø,0Ø/B¨{×/BÑ/BÓ/Dñ 2 ð2Ø #ð2à"%ð2ð(,ð2ð$/ð 2ðJ]ò 2óñ2r!rc ó —eZdZdZediej «fdedeede ee fdede f d„«Z edifdedeede ee ffd „«Z y) ÚDynamoDBzYProvides factory methods for integrations between the LaunchDarkly SDK and DynamoDB. NÚ table_namerÚ dynamodb_optsrrcó4—t|||«}t||«S)a›Creates a DynamoDB-backed implementation of :class:`ldclient.interfaces.FeatureStore`. For more details about how and why you can use a persistent feature store, see the `SDK reference guide `_. To use this method, you must first install the ``boto3`` package for the AWS SDK. Then, put the object returned by this method into the ``feature_store`` property of your client configuration (:class:`ldclient.config.Config`). :: from ldclient.integrations import DynamoDB store = DynamoDB.new_feature_store("my-table-name") config = Config(feature_store=store) Note that the DynamoDB table must already exist; the LaunchDarkly SDK does not create the table automatically, because it has no way of knowing what additional properties (such as permissions and throughput) you would want it to have. The table must have a partition key called "namespace" and a sort key called "key", both with a string type. By default, the DynamoDB client will try to get your AWS credentials and region name from environment variables and/or local configuration files, as described in the AWS SDK documentation. You may also pass configuration settings in ``dynamodb_opts``. :param table_name: the name of an existing DynamoDB table :param prefix: an optional namespace prefix to be prepended to all DynamoDB keys :param dynamodb_opts: optional parameters for configuring the DynamoDB client, as defined in the `boto3 API `_ :param caching: specifies whether local caching should be enabled and if so, sets the cache properties; defaults to :func:`ldclient.feature_store.CacheConfig.default()` )rr)r/rr0rrs rr zDynamoDB.new_feature_store=s €ôD)¨°V¸]ÓKˆÜ" 4¨Ó1Ð1r!có—t|||«S)a Creates a DynamoDB-backed Big Segment store. Big Segments are a specific type of user segments. For more information, read the LaunchDarkly documentation: https://docs.launchdarkly.com/home/users/big-segments To use this method, you must first install the ``boto3`` package for the AWS SDK. Then, put the object returned by this method into the ``store`` property of your Big Segments configuration (see :class:`ldclient.config.Config`). :: from ldclient.config import Config, BigSegmentsConfig from ldclient.integrations import DynamoDB store = DynamoDB.new_big_segment_store("my-table-name") config = Config(big_segments=BigSegmentsConfig(store=store)) Note that the DynamoDB table must already exist; the LaunchDarkly SDK does not create the table automatically, because it has no way of knowing what additional properties (such as permissions and throughput) you would want it to have. The table must have a partition key called "namespace" and a sort key called "key", both with a string type. By default, the DynamoDB client will try to get your AWS credentials and region name from environment variables and/or local configuration files, as described in the AWS SDK documentation. You may also pass configuration settings in ``dynamodb_opts``. :param table_name: the name of an existing DynamoDB table :param prefix: an optional namespace prefix to be prepended to all DynamoDB keys :param dynamodb_opts: optional parameters for configuring the DynamoDB client, as defined in the `boto3 API `_ r)r/rr0s rÚnew_big_segment_storezDynamoDB.new_big_segment_storebs€ô@(¨ °F¸MÓJÐJr!)r"r#r$r%r'rr(r)rrrrr r3r,r!rr.r.9s¯„ñðà04Ø;=Ø/B¨{×/BÑ/BÓ/Dñ"2 cð"2Ø"*¨3¡-ð"2à)0°°c°Ñ):ð"2ð$/ð"2ðJ]ò"2óð"2ðHØEIÐlnñK¨#ðK°xÀ±}ðKÐZaÐbeÐgjÐbjÑZkòKóñKr!r.có´—eZdZdZdZdZdZedddej«ifde de de ded e e e fd ef d „«Zedddifde de de d e e e fd ef d „«Zy )ÚRediszVProvides factory methods for integrations between the LaunchDarkly SDK and Redis. zredis://localhost:6379/0réÚurlrÚmax_connectionsrÚ redis_optsrcóF—t|||«}t||«}||_|S)aõ Creates a Redis-backed implementation of :class:`~ldclient.interfaces.FeatureStore`. For more details about how and why you can use a persistent feature store, see the `SDK reference guide `_. To use this method, you must first install the ``redis`` package. Then, put the object returned by this method into the ``feature_store`` property of your client configuration (:class:`ldclient.config.Config`). :: from ldclient.config import Config from ldclient.integrations import Redis store = Redis.new_feature_store() config = Config(feature_store=store) :param url: the URL of the Redis host; defaults to ``DEFAULT_URL`` :param prefix: a namespace prefix to be prepended to all Redis keys; defaults to ``DEFAULT_PREFIX`` :param caching: specifies whether local caching should be enabled and if so, sets the cache properties; defaults to :func:`ldclient.feature_store.CacheConfig.default()` :param redis_opts: extra options for initializing Redis connection from the url, see `redis.connection.ConnectionPool.from_url` for more details. )r rÚ_core)r7rr8rr9rÚwrappers rr zRedis.new_feature_storeŒs*€ô<& c¨6°:Ó>ˆÜ% d¨GÓ4ˆØˆŒ ؈r!có—t|||«S)a9 Creates a Redis-backed Big Segment store. Big Segments are a specific type of user segments. For more information, read the LaunchDarkly documentation: https://docs.launchdarkly.com/home/users/big-segments To use this method, you must first install the ``redis`` package. Then, put the object returned by this method into the ``store`` property of your Big Segments configuration (see :class:`ldclient.config.Config`). :: from ldclient.config import Config, BigSegmentsConfig from ldclient.integrations import Redis store = Redis.new_big_segment_store() config = Config(big_segments=BigSegmentsConfig(store=store)) :param url: the URL of the Redis host; defaults to ``DEFAULT_URL`` :param prefix: a namespace prefix to be prepended to all Redis keys; defaults to ``DEFAULT_PREFIX`` :param redis_opts: extra options for initializing Redis connection from the url, see `redis.connection.ConnectionPool.from_url` for more details. r )r7rr8r9s rr3zRedis.new_big_segment_store¯s€ô8% S¨&°*Ó=Ð=r!N)r"r#r$r%Ú DEFAULT_URLr&ÚDEFAULT_MAX_CONNECTIONSr'rr(r)r*rrrr rr3r,r!rr5r5…sׄñà,€KØ#€NØ ÐàØ#=Ø&4Ø/1Ø/B¨{×/BÑ/BÓ/DØ79ñ ˜sð Ø"%ð à+.ð ð$/ð ð'+¨3°¨8¡nð ð?Rò óð ðDØ'AØ*8Ø35Ø;=ñ> 3ð>Ø&)ð>à/2ð>ð+/¨s°C¨x©.ð>ðCRò>óñ>r!r5c óD—eZdZdZe d deedededede f d„«Z y) ÚFileszDProvides factory methods for integrations with filesystem data. ÚpathsÚ auto_updateÚ poll_intervalÚ force_pollingrc󇇇‡—ˆˆˆˆfd„S)a& Provides a way to use local files as a source of feature flag state. This would typically be used in a test environment, to operate using a predetermined feature flag state without an actual LaunchDarkly connection. To use this component, call ``new_data_source``, specifying the file path(s) of your data file(s) in the ``paths`` parameter; then put the value returned by this method into the ``update_processor_class`` property of your LaunchDarkly client configuration (:class:`ldclient.config.Config`). :: from ldclient.integrations import Files data_source = Files.new_data_source(paths=[ myFilePath ]) config = Config(update_processor_class=data_source) This will cause the client not to connect to LaunchDarkly to get feature flags. The client may still make network connections to send analytics events, unless you have disabled this in your configuration with ``send_events`` or ``offline``. The format of the data files is described in the SDK Reference Guide on `Reading flags from a file `_. Note that in order to use YAML, you will need to install the ``pyyaml`` package. If the data source encounters any error in any file-- malformed content, a missing file, or a duplicate key-- it will not load flags from any of the files. :param paths: the paths of the source files for loading flag data. These may be absolute paths or relative to the current working directory. Files will be parsed as JSON unless the ``pyyaml`` package is installed, in which case YAML is also allowed. :param auto_update: (default: false) True if the data source should watch for changes to the source file(s) and reload flags whenever there is a change. The default implementation of this feature is based on polling the filesystem, which may not perform well; if you install the ``watchdog`` package, its native file watching mechanism will be used instead. Note that auto-updating will only work if all of the files you specified have valid directory paths at startup time. :param poll_interval: (default: 1) the minimum interval, in seconds, between checks for file modifications-- used only if ``auto_update`` is true, and if the native file-watching mechanism from ``watchdog`` is not being used. :param force_polling: (default: false) True if the data source should implement auto-update via polling the filesystem even if a native mechanism is available. This is mainly for SDK testing. :return: an object (actually a lambda) to be stored in the ``update_processor_class`` configuration property có$•—t||‰‰‰‰«S)Nr )ÚconfigÚstoreÚreadyrCrErBrDs €€€€rúz'Files.new_data_source..þsø€¬_¸UÀEÈ5ÐR]Ð_lÐn{Ó-|€r!r,)rBrCrDrEs````rÚnew_data_sourcezFiles.new_data_sourceÑs û€öZ}Ð|r!N)FéF) r"r#r$r%r'rr)ÚboolÚfloatÚobjectrLr,r!rrArAÍsZ„ñðà*/Ø-.Ø,1ñ,}˜t C™yð,}Ø%)ð,}à',ð,}ð(,ð,}ð7=ò,}óñ,}r!rAN)r%Úldclient.feature_storerÚldclient.feature_store_helpersrÚ6ldclient.impl.integrations.consul.consul_feature_storerÚ>ldclient.impl.integrations.dynamodb.dynamodb_big_segment_storerÚ:ldclient.impl.integrations.dynamodb.dynamodb_feature_storerÚ1ldclient.impl.integrations.files.file_data_sourcer Ú8ldclient.impl.integrations.redis.redis_big_segment_storer Ú4ldclient.impl.integrations.redis.redis_feature_storer Úldclient.interfacesrÚtypingrrrrrrr.r5rAr,r!rúr[s`ðñõ /Ý>ÝZÝcÝ`ÝMÝZÝWÝ/ç5Õ5÷$2ñ$2÷NIKñIK÷XF>ñF>÷P1}ò1}r!