launchpy 0.4.9__tar.gz → 0.5.0__tar.gz

{launchpy-0.4.9/launchpy.egg-info → launchpy-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: launchpy
-Version: 0.4.9
+Version: 0.5.0
 Summary: Adobe Launch API wrapper
 Author-email: Julien Piccini <piccini.julien@gmail.com>
 License: Apache License 2.0

{launchpy-0.4.9 → launchpy-0.5.0}/docs/cli.md

@@ -10,6 +10,7 @@ This document provides an overview of the command line interface (CLI) for `laun
     - [Instantiation](#instantiation)
       - [create\_config\_file](#create_config_file)
       - [config](#config)
+      - [change\_org](#change_org)
       - [get\_properties](#get_properties)
       - [create\_property](#create_property)
       - [delete\_property](#delete_property)
@@ -34,6 +35,9 @@ This document provides an overview of the command line interface (CLI) for `laun
     - [Synchronizer Layer Commands](#synchronizer-layer-commands)
       - [check\_component](#check_component)
       - [sync](#sync)
+      - [sync\_rules](#sync_rules)
+      - [sync\_data\_elements](#sync_data_elements)
+      - [sync\_extensions](#sync_extensions)
       - [rename\_component](#rename_component)
       - [get\_targets](#get_targets)
       - [upgrade\_extension](#upgrade_extension)
@@ -99,8 +103,9 @@ The config method also take individual parameters as arguments, which would over
 
 #### create_config_file
 Create a config file to store your credentials and other necessary information for using `launchpy`. This is a one-time setup step that allows you to save your configuration for future use.\
-Arguments
-`-fn`, `--file_name`: The name of the config file to be created. If not provided, it defaults to `launchpy_config.json`.\
+Arguments:
+`-fn`, `--file_name`: The name of the config file to be created. If not provided, it defaults to `launchpy_config.json`.
+`-m`, `--multi_org`: Flag. If present, generate a config file template for multiple organizations (a JSON list, each entry with its own `org_name`) instead of the default single-organization template (a JSON object).
 
 You can create a config file by running the following command:
 
@@ -109,6 +114,29 @@ python -m launchpy.cli
 (Cmd) create_config_file
 ```
 
+If you need to connect to several Adobe Experience Platform organizations from the same CLI session, generate a multi-org template instead:
+
+```bash
+python -m launchpy.cli
+(Cmd) create_config_file --multi_org
+```
+
+This produces a JSON list of config blocks (instead of a single JSON object), where each block requires an `org_name` key used to reference that organization, for example:
+
+```json
+[
+    {
+        "org_id": "<orgID>",
+        "client_id": "<client_id>",
+        "secret": "<YourSecret>",
+        "scopes": "<scopes>",
+        "org_name": "<org_name>"
+    }
+]
+```
+
+You can duplicate that block for each organization you want to connect to, giving each a unique `org_name`. See the [config](#config) and [change_org](#change_org) commands below for how to use this file.
+
 
 #### config
 Setup the API connection to use the full capacity of the CLI. 
@@ -119,6 +147,7 @@ Arguments
 `-sc`,`--scopes`: The scopes that define the permissions for your API connection. This is a required parameter.
 `-cf`,`--config_file`: The path to the config file that contains your credentials and other necessary information.
 `-p`,`--property` : The property name to be used and directly instantiated the property layer. This is an optional parameter.
+`-on`,`--org_name`: The organization name to use when your `--config_file` is a multi-org config file (see [create_config_file](#create_config_file)). This is an optional parameter, it defaults to the first organization found in the file (or `default` when using individual parameters).
 
 Example via parameters:
 ```bash
@@ -156,6 +185,27 @@ It also supports direct access to the property layer by providing the property n
 python -m launchpy.cli --config_file <path_to_your_config_file> --property <your_property_name>
 ```
 
+Example with a multi-org config file, connecting directly to the `client_a` organization:
+```bash
+python -m launchpy.cli
+(Cmd) config --config_file <path_to_your_multi_org_config_file> --org_name client_a
+launchpy:client_a>
+```
+
+When in a non-multi-org environment, the prompt of the CLI will be `launchpy>`, and when in a multi-org environment, the prompt will be `launchpy:<org_name>`, where `<org_name>` is the name of the organization you are currently connected to.\
+By default, the first organization found in the multi-org config file will be used if no `--org_name` is provided. You can switch between organizations using the `change_org` command.
+
+#### change_org
+Switch the current CLI session to another organization that has already been loaded from a multi-org config file (via `config` or `--config_file` at startup). This avoids re-running `config` when you need to move between organizations.\
+Arguments:
+`org_name`: The name of the organization to switch to, matching one of the `org_name` values in your multi-org config file. This is a required parameter.
+
+```bash
+python -m launchpy.cli
+(Cmd) config --config_file <path_to_your_multi_org_config_file>
+launchpy:client_a> change_org client_b
+launchpy:client_b>
+```
 
 #### get_properties
 Retrieve a list of properties associated with your Adobe Developer Project. This command allows you to view the properties that you have access to and can manage using `launchpy`.\
@@ -194,9 +244,11 @@ launchpy> delete_property "Property Name"
 
 #### extract_property
 This method allows you to extract the details of a specific property and save them to a folder.\
-The folder name would be the name of the property, it will contains sub folders for each rules.\
+By default, the folder name would be the name of the property, and it will contain sub folders for each rule.\
 Arguments:
 `name`: The name of the property to extract. This is a required parameter.
+`-p`, `--published_version`: Boolean. Extract only the latest published version of the components instead of the current (development) version. Default False. Possible values: `True`, `False`
+`-f`, `--folder`: The folder to extract the property into. This is an optional parameter, if not provided, it defaults to a folder named after the property in the current working directory.
 
 This can be useful for searching code or for backup purposes. 
 
@@ -206,6 +258,12 @@ python -m launchpy.cli -cf <path_to_your_config_file>
 launchpy> extract_property "Property Name"
 ```
 
+Example extracting the latest published version into a specific folder:
+```bash
+python -m launchpy.cli -cf <path_to_your_config_file>
+launchpy> extract_property "Property Name" --published_version True --folder "./exports/property_name"
+```
+
 
 #### load_property
 This method load the property layer for a specific property, allowing you to access and manage that property directly.
@@ -248,62 +306,62 @@ Once you have instantiated the property layer for a specific property, you can a
 #### get_extensions
 Get all extensions in the property and list them.\
 Arguments:
-`-s`, `--save`: Boolean. Save extensions to a CSV file. Default False. Possible values: `True`, `False`
+`-s`, `--save`: Flag. Save extensions to a CSV file. Default False.
 
 ```bash
-property_name> get_extensions -s True
+property_name> get_extensions -s
 ```
 
 #### get_extension
 Get details of a specific extension in the property.\
 Arguments:
 `name`: The name of the extension to retrieve details for. This is a required parameter.
-`-s`, `--save`: Boolean. Save the extension details to a JSON file. Default False. Possible values: `True`, `False`
+`-s`, `--save`: Flag. Save the extension details to a JSON file. Default False.
 
 ```bash
-property_name> get_extension "Extension Name" -s True
+property_name> get_extension "Extension Name" -s
 ```
 
 #### get_rules
 Get all rules in the property and list them.\
 Arguments:
 `-n`, `--name`: The name of the rule to filter the results (partial match, non-case sensitive). This is an optional parameter.
-`-s`, `--save`: Boolean. Save rules to a CSV file. Default False. Possible values: `True`, `False`
+`-s`, `--save`: Flag. Save rules to a CSV file. Default False.
 
 ```bash
-property_name> get_rules -n "Rule Name" -s True
+property_name> get_rules -n "Rule Name" -s
 ```
 
 #### get_rule
 Get details of a specific rule in the property.\
 Arguments:
 `name`: The name of the rule to retrieve details for. This is a required parameter.
-`-s`, `--save`: Boolean. Save the rule details to a JSON file. Default False. Possible values: `True`, `False`
+`-s`, `--save`: Flag. Save the rule details to a JSON file. Default False.
 
 ```bash
-property_name> get_rule "Rule Name" -s True
+property_name> get_rule "Rule Name" -s
 ```
 
 #### get_rules_components
 Get all rule components, and save them to a CSV file if specified. Intended to be used for all components, but can be filtering.\
 Arguments:
-`-s`, `--save`: Boolean. Save rules components to a CSV file. Default False. Possible values: `True`, `False`
+`-s`, `--save`: Flag. Save rules components to a CSV file. Default False.
 `-rn`, `--rule_name`: (Partial) Name of the rule to get components for. This is an optional parameter.
 `-rid`, `--rule_id`: ID of the rule to get components for. This is an optional parameter, if both `rule_name` and `rule_id` are provided, it will use `rule_id`.
 
 ```bash
-property_name> get_rules_components -s True
+property_name> get_rules_components -s
 ```
 
 #### get_rule_components
 Get all components for a specific rule by name or ID. Way more effective than the other methods and provide more details.\
 Arguments:
-`-s`, `--save`: Boolean. Save the rule components to a JSON file. Default False. Possible values: `True`, `False`
+`-s`, `--save`: Flag. Save the rule components to a JSON file. Default False.
 `-rn`, `--rule_name`: (Partial) Name of the rule to get components for. This is an optional parameter.
 `-rid`, `--rule_id`: ID of the rule to get components for. This is an optional parameter, if both `rule_name` and `rule_id` are provided, it will use `rule_id`.
 
 ```bash
-property_name> get_rule_components -rn "Rule Name" -s True
+property_name> get_rule_components -rn "Rule Name" -s
 ```
 
 #### get_data_elements
@@ -320,10 +378,10 @@ property_name> get_data_elements -n "Data Element Name" -s True
 Get details of a specific data element in the property.\
 Arguments:
 `name`: The name of the data element to retrieve details for. This is a required parameter.
-`-s`, `--save`: Boolean. Save the data element details to a JSON file. Default False. Possible values: `True`, `False`
+`-s`, `--save`: Flag. Save the data element details to a JSON file. Default False.
 
 ```bash
-property_name> get_data_element "Data Element Name" -s True
+property_name> get_data_element "Data Element Name" -s
 ```
 
 #### get_latest_published_version
@@ -331,20 +389,20 @@ Get the latest published version of a specific component in the property.\
 Arguments:
 `-n`, `--name`: The name of the component to get the latest published version for. This is a required parameter.
 `-t`, `--type`: The type of the component (e.g. 'rule', 'data_element', 'extension') to get the latest published version for. This is a required parameter.
-`-s`, `--save`: Boolean. Save the latest published version details to a JSON file. Default False. Possible values: `True`, `False`
+`-s`, `--save`: Flag. Save the latest published version details to a JSON file. Default False.
 
 ```bash
-property_name> get_latest_published_version -n "Component Name" -t "rule" -s True
+property_name> get_latest_published_version -n "Component Name" -t "rule" -s
 ```
 
 #### get_libraries
 Get all libraries in the property and list them.\
 Arguments:
-`-s`, `--save`: Boolean. Save libraries to a CSV file. Default False. Possible values: `True`, `False`
+`-s`, `--save`: Flag. Save libraries to a CSV file. Default False.
 `-st`, `--state`: Filter by library state. Possible values: 'development' (default), 'submitted', 'approved', 'rejected', 'published'. This is an optional parameter.
 
 ```bash
-property_name> get_libraries -s True -st "development"
+property_name> get_libraries -s -st "development"
 ```
 
 #### delete_library
@@ -382,10 +440,10 @@ Check if a specific component is in sync between the base property and target pr
 Arguments:
 `-n`, `--name`: The name of the component to check for synchronization. This is a required parameter.
 `-id`, `--id`: ID of the component to check (overrides name if both provided)
-`-p`, `--published` : Boolean. Check the synchronization based on the latest published version of the component. Default False. Possible values: `True`, `False`
+`-p`, `--published` : Flag. Check the synchronization based on the latest published version of the component. Default False.
 
 ```bash
-synchronizer:Base_Property_Name> check_component -n "Component Name" -p True
+synchronizer:Base_Property_Name> check_component -n "Component Name" -p
 ```
 
 #### sync
@@ -393,11 +451,45 @@ Synchronize a specific component between the base property and target properties
 Arguments:
 `-n`, `--name`: The name of the component to synchronize. This is a required parameter.
 `-id`, `--id`: ID of the component to synchronize (overrides name if both provided)
-`-p`, `--published` : Boolean. Synchronize the latest published version of the component. Default `False`. Possible values: `True`, `False`
-`-f`, `--force` : Boolean. Create the component if it does not exist. Default `True`. Possible values: `True`, `False`
+`-p`, `--published` : Flag. Synchronize the latest published version of the component. Default False.
+`-c`, `--create` : Flag. Create the component if it does not exist. Default False.
+`-v`, `--verbose` : Flag. Print detailed information about the sync process. Default False.
+
+```bash
+synchronizer:Base_Property_Name> sync -n "Component Name" -p -c
+```
+
+#### sync_rules
+Synchronize all rules between the base property and target properties in a single call, instead of syncing them one by one with [sync](#sync).\
+Arguments:
+`-r`, `--regex`: Regex pattern to filter rules by name (partial match, non-case sensitive). This is an optional parameter, if not provided, all rules are synced.
+`-c`, `--create` : Flag. Create rules that do not exist in the destination property. Default False.
+`-p`, `--published` : Flag. Sync the latest published version of the rules. Default False.
+
+```bash
+synchronizer:Base_Property_Name> sync_rules -r "Rule Name" -c
+```
+
+#### sync_data_elements
+Synchronize all data elements between the base property and target properties in a single call, instead of syncing them one by one with [sync](#sync).\
+Arguments:
+`-r`, `--regex`: Regex pattern to filter data elements by name (partial match, non-case sensitive). This is an optional parameter, if not provided, all data elements are synced.
+`-c`, `--create` : Flag. Create data elements that do not exist in the destination property. Default False.
+`-p`, `--published` : Flag. Sync the latest published version of the data elements. Default False.
+
+```bash
+synchronizer:Base_Property_Name> sync_data_elements -r "Data Element Name" -c
+```
+
+#### sync_extensions
+Synchronize all extensions between the base property and target properties in a single call, instead of syncing them one by one with [sync](#sync).\
+Arguments:
+`-r`, `--regex`: Regex pattern to filter extensions by name (partial match, non-case sensitive). This is an optional parameter, if not provided, all extensions are synced.
+`-c`, `--create` : Flag. Create extensions that do not exist in the destination property. Default False.
+`-v`, `--verbose` : Flag. Print detailed information about the sync process. Default False.
 
 ```bash
-synchronizer:Base_Property_Name> sync -n "Component Name" -p True -f True
+synchronizer:Base_Property_Name> sync_extensions -r "Extension Name" -c
 ```
 
 #### rename_component

{launchpy-0.4.9 → launchpy-0.5.0}/docs/getstarted.md

@@ -23,17 +23,49 @@ import launchpy as lp
 lp.createConfigFile()
 ```
 
+It takes these parameters: 
+* filename : OPTIONAL : The name of the JSON file to create. Default: "config_launch.json"
+* auth_type : OPTIONAL : The type of authentication to use. Default: "oauthV2".
+* scope : OPTIONAL : The scope of the authentication. Default: "https://ims-na1.adobelogin.com/s/ent_reactor_admin_sdk".
+  if any problem occurs, you can update the scope to "https://ims-na1.adobelogin.com/s/ent_reactor_sdk"
+* multi_org : OPTIONAL : If set to True, it will create a multi-org config file. Default: False.
+
+
+The config JSON will look like: 
+
+```JSON
+{
+    "org_id": "<orgID>",
+    "client_id": "<client_id>",
+    "secret": "<YourSecret>",
+    "scopes": "<scopes>",
+}
+```
+
 This will create a JSON and you will need to fill it with the information available in your adobe io account.
 
 **NOTE**: scope in the config file has evolved over time so you can change it. Following this [link](https://www.adobe.io/authentication/auth-methods.html#!AdobeDocs/adobeio-auth/master/JWT/Scopes.md) to see the different scope possible.\
 You can change the `scope` attribute for one of these values: `"https://ims-na1.adobelogin.com/s/ent_reactor_admin_sdk"` or `"https://ims-na1.adobelogin.com/s/ent_reactor_sdk"`
 By default, I will test the dev scope if the scope provided fails. So normally nothing you need to do.
 
-**NOTE 2**: There is a possibility till end of 2024 to use the JWT.\
-launchpy supports both `jwt` and `oauthV2` authentication.\
-By default the latest version will try to use the `oauthV2`.\
-You can specify the keys generated in the config file by using the `auth_type` parameter.\
-Possible values : `oauthV2` (default) or `jwt`
+
+### 3. Bis Multi Org Setup
+
+In case you have a multi IMS Org setup and you would need to do synchronization between different IMS Org, you can use the `multi_org` parameter to create a multi-org config file.\
+This will change your JSON file into a list, and add the `org_name` attribute.\
+So your config file will look like this: 
+```JSON
+[
+    {
+    "org_id": "<orgID>",
+    "client_id": "<client_id>",
+    "secret": "<YourSecret>",
+    "scopes": "<scopes>",
+    "org_name": "<org_name>"
+    }
+]
+
+``` 
 
 
 ## 4. Import the configuration file
@@ -45,6 +77,30 @@ I would recommend to store the config file and the key in the folder that you ar
 lp.importConfigFile('myconfig.json')
 ```
 
+### 4. Bis Multi Org Setup
+
+In case you are loading multi org setup, you need to have the `org_name` attribute filled.\
+So your config file will look like this: 
+```JSON
+[
+    {
+    "org_id": "<orgID>",
+    "client_id": "<client_id>",
+    "secret": "<YourSecret>",
+    "scopes": "<scopes>",
+    "org_name": "org_name1"
+    },
+    {
+    "org_id": "<orgID>",
+    "client_id": "<client_id>",
+    "secret": "<YourSecret>",
+    "scopes": "<scopes>",
+    "org_name": "org_name2"
+    }
+]
+```
+
+
 ## 5. Instantiate the Admin class & get Company ID to retrieve properties
 
 Once all of these setup steps are completed, you can instantiate the `Admin` class.

{launchpy-0.4.9 → launchpy-0.5.0}/docs/releases.md

@@ -3,11 +3,29 @@
 This page gathered the changes made between version of the launchpy module.\
 This has been started after the 0.3.0 release.\
 
+## 0.5.0
+* Adding option to extract only the latest published version of the artifacts when extracting a property. This is available in the CLI with the `-p` or `--published_version` flag and in the `extractProperty` function with the `publishedVersion` parameter. 
+* Fixing the `create_property` method in the CLI
+* Adding support for multi-org config files.
+* Adding support for multi-org instantiation in the synchronizer module.
+* Adding capability to sync extensions via syncComponent method.
+* Adding `sync_rules` capabilitiy in the CLI and `syncRules` in synchronizer module.
+* Adding `sync_extensions` capabilitiy in the CLI and `syncExtensions` in synchronizer module.
+* Adding `sync_data_elements` capabilitiy in the CLI and `syncDataElements` in synchronizer module.
+* Fixing the `createTargetsLibrary` method in the synchronizer where using existing library that contained rules not touched by the synchronizer would delete them. Now it will keep them and only update the ones that are in the source property.
+* `extractProperty` can now extract the elements as they are in their published version. This is available in the CLI with the `-p` or `--published_version` flag and in the `extractProperty` function with the `publishedVersion` parameter.
+* `extractProperty` has a new parameter `folder` that allows you to specify the folder where the property will be extracted. If None, a folder named after the property name will be created in the current working directory.
+
+
 ## 0.4.9
 * fixing httpx dependency requirement
 * extractProperty will now also extract Data Elements and Extensions configurations in separate folders.
 * fix the argument handling for linkedLibrary in CLI.
-* Change of the `force` parameter to `create` in the synchronizer CLI for better understanding of the action. `create` is now default to `False`. The synchronizer module keeps its long name `forceCreation` for backward compatibility and better understanding of the action. Also turning it to `False` by default. 
+* Change of the `force` parameter to `create` in the synchronizer CLI for better understanding of the action. `create` is now default to `False`. The synchronizer module keeps its long name `forceCreation` for backward compatibility and better understanding of the action. Also turning it to `False` by default. \
+Patch:
+* adding a `verbose` parameter to the synchronizer CLI for better understanding of the process. Default to `False`.
+* adding a `verbose` parameter to the synchronizer module for better understanding of the process. Default to `False`.
+* fixing default value for `create` parameter and its documentation in the CLI.
 
 ## 0.4.8
 * Adding the `clear` method in CLI

{launchpy-0.4.9 → launchpy-0.5.0}/docs/synchronizer.md

@@ -137,7 +137,7 @@ You can pass down a list of component names or componentIds.\
 It takes 3 arguments:\
 Arguments:
 * componentsName : REQUIRED : The list of component names to sync
-* componentsId : REQUIRED : The list of component ID to sync*
+* componentsId : REQUIRED : The list of component ID to sync
 * publishedVersion : OPTIONAL : if you want to take the version that has been published
 
 ## syncFromLibrary
@@ -158,6 +158,30 @@ By default, the method will sync the components present in the library as they a
 If the `publishedVersion` is set to True, it will try to sync the version that has been published in the base property to the targets.\
 If the `libraryLinked` is set to `False` and the `publishedVersion` is set to `False` (default), it will try to sync the latest version of the components present in the base property library to the targets.\
 
+## syncExtensions
+
+This method allows you to sync the extension(s) from the base property to the target properties.\
+It will check if the extension is already installed in the target property, if not, it will install it if you have used the forceCreation parameter. Note that we cannot guarantee the same version as only the latest version is available for installation.\
+If the extension(s) is already installed, it will check if the settings are the same, if not, it will update the settings to match the base property.\
+Arguments:
+* regex : OPTIONAL : If you want to filter the extensions name to sync based on a regex pattern. Default: None (sync all extensions)
+* forceCreation : OPTIONAL : If set to True, will force the creation of the extension even if it already exists. Default: False
+
+## syncDataElements
+Synchronizing the data elements in the base property to the target properties.
+Arguments:
+*  regex : OPTIONAL : If you want to filter the data elements to sync based on a regex pattern. Default: None (sync all data elements)
+*  forceCreation : OPTIONAL : If set to True, it will sync the data elements even if they do not exist in the target properties. If set to False, it will only sync the data elements that already exist in the target properties. Default: False.
+*  publishedVersion : OPTIONAL : If set to True, it will sync the latest published version of the data elements. Default: False.
+
+## SyncRules
+It will synchronize the rules in the base property to the target properties.
+Arguments:
+*  regex : OPTIONAL : If you want to filter the rules to sync based on a regex pattern. Default: None (sync all rules)
+*  forceCreation : OPTIONAL : If set to True, it will sync the rules even if they do not exist in the target properties. If set to False, it will only sync the rules that already exist in the target properties. Default: False.
+*  publishedVersion : OPTIONAL : If set to True, it will sync the latest published version of the rules. Default: False.
+
+
 ## createTargetsLibrary
 
 The synchronizer will automatically track the component that has been updated via the module.\

{launchpy-0.4.9 → launchpy-0.5.0}/launchpy/__init__.py

@@ -60,7 +60,15 @@ async def write_all_data_elements(data_elements_list, folder, header):
             json.dump(data_element, f, indent=4)
 
 
-def extractProperty(property: dict | Property):
+def extractProperty(property: dict | Property, publishedVersion: bool = False,folder: str = None):
+    """
+    Extract the rules, Data Elements and Extensions configuration for a given property and save them in a folder named after the property.
+    Arguments:
+        property: dict | Property: The property to extract. Can be a Property object or a dictionary containing the property data.
+        publishedVersion: bool: If True, only the latest published version of each rule will be extracted. If False, all rules as latest state will be extracted.
+            For rules that are not yet published, the latest state will be extracted regardless of the value of this parameter.
+        folder : str: The folder where the property will be extracted. If None, a folder named after the property will be created in the current working directory.
+    """
     if property is None:
         raise ValueError("Property is None")
     elif type(property) is not Property and type(property) is dict:
@@ -68,17 +76,48 @@ def extractProperty(property: dict | Property):
             property = Property(property)
         else:
             raise ValueError("Property is not of type Property")
-    folder = __safe_name__(property.name)
+    if folder is None:
+        folder = __safe_name__(property.name)
     Path(folder).mkdir(parents=True, exist_ok=True)
     rules = property.getRules()
+    if publishedVersion:
+        published_rules = []
+        for rule in rules:
+            revisions = property.getRevisions(rule)
+            try:
+                publishedRule = property.getLatestPublishedVersion(revisions)
+                published_rules.append(publishedRule)
+            except Exception as e:
+                published_rules.append(rule)
+        rules = published_rules
     asyncio.run(process_all_rules(rules, folder, property.header))
     dataElements = property.getDataElements()
+    if publishedVersion:
+        published_data_elements = []
+        for data_element in dataElements:
+            revisions = property.getRevisions(data_element)
+            try:
+                publishedDataElement = property.getLatestPublishedVersion(revisions)
+                published_data_elements.append(publishedDataElement)
+            except Exception as e:
+                published_data_elements.append(data_element)
+        dataElements = published_data_elements
     dataElements_folder = Path(folder) / "data_elements"
     Path(dataElements_folder).mkdir(parents=True, exist_ok=True)
     asyncio.run(write_all_data_elements(dataElements, dataElements_folder, property.header))
     extension_folder = Path(folder) / "extensions"
     extension_folder.mkdir(parents=True, exist_ok=True)
     extensions = property.getExtensions()
+    if publishedVersion:
+        published_extensions = []
+        for extension in extensions:
+            revisions = property.getRevisions(extension)
+            try:
+                publishedExtension = property.getLatestPublishedVersion(revisions)
+                published_extensions.append(publishedExtension)
+            except Exception as e:
+                published_extensions.append(extension)
+        extensions = published_extensions
     for extension in extensions:
         extension_name = __safe_name__(extension['attributes']['name'])
         file_path = extension_folder / f"{extension_name}.json"

launchpy-0.5.0/launchpy/__version__.py

@@ -0,0 +1 @@
+__version__ = "0.5.0"

{launchpy-0.4.9 → launchpy-0.5.0}/launchpy/admin.py

@@ -6,12 +6,14 @@ from .property import Property
 
 class Admin:
 
-    def __init__(self,config_object:dict=config.config_object,header:dict=config.header):
+    def __init__(self, _connector: connector.AdobeRequest = None, org_name: str = None):
         """
-        Instantiate the connector for the Login class
+        Instantiate the connector for the Login class.
+        Arguments:
+            _connector : OPTIONAL : Pass an existing AdobeRequest instance (internal use / multi-org).
+            org_name : OPTIONAL : The name of the organization (internal use / multi-org).
         """
-        self.connector = connector.AdobeRequest(
-            config_object=config_object, header=header)
+        self.connector = _connector if _connector is not None else connector.AdobeRequest(org_name=org_name)
         self.header = self.connector.header
         self.COMPANY_ID = ""
         self.COMPANY_NAME  = ""