pyegeria 5.2.0.42.2__tar.gz → 5.4.9.5__tar.gz

pyegeria-5.4.9.5/MANIFEST.in

@@ -0,0 +1,3 @@
+   include LICENSE
+   include README.md
+   recursive-include md_processing/data *.json *.py

pyegeria-5.4.9.5/PKG-INFO

@@ -0,0 +1,216 @@
+Metadata-Version: 2.4
+Name: pyegeria
+Version: 5.4.9.5
+Summary: A python client for Egeria
+Author-email: Dan Wolfson <dan.wolfson@pdr-associates.com>
+License-Expression: Apache-2.0
+Keywords: egeria,metadata,governance
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: httpx
+Requires-Dist: rich>=14.2
+Requires-Dist: validators
+Requires-Dist: urllib3
+Requires-Dist: requests
+Requires-Dist: jupyter
+Requires-Dist: click
+Requires-Dist: trogon
+Requires-Dist: psycopg2-binary>=2.9.11
+Requires-Dist: jupyter-notebook-parser
+Requires-Dist: loguru
+Requires-Dist: inflect
+Requires-Dist: pydantic>=2.12.3
+Requires-Dist: pydantic-settings>=2.10.1
+Requires-Dist: pydevd-pycharm>=253.27642.35
+Requires-Dist: wcwidth
+Requires-Dist: altair
+Requires-Dist: mcp>=0.1
+Requires-Dist: markers>=0.3.0
+Requires-Dist: pytest-asyncio>=1.2.0
+Requires-Dist: python-dotenv>=1.1.1
+Provides-Extra: test
+Requires-Dist: pytest; extra == "test"
+Dynamic: license-file
+
+<!-- SPDX-License-Identifier: CC-BY-4.0 -->
+<!-- Copyright Contributors to the ODPi Egeria project. -->
+
+![Egeria Logo](https://egeria-project.org/assets/images/egeria-header.png)
+
+[![GitHub](https://img.shields.io/github/license/odpi/egeria)](LICENSE)
+
+
+# pyegeria: a python client for Egeria
+
+A lightweight Python 3.12+ client and CLI for the Egeria open metadata and governance platform. It helps you configure and operate Egeria services and work with metadata (assets, glossaries, lineage, etc.) from Python, with examples, tests, and documented report formats.
+
+This is a package for easily using the Egeria
+open metadata environment from python. Details about the
+open source Egeria project can be found at [Egeria Project](https://egeria-project.org).
+
+This package is in active development. There is initial
+support for many of Egeria's services including configuration and operation.  This client depends on 
+This release supports Egeria 5.1 - although most of the functions may work on earlier versions of Egeria as well. 
+
+The code is organized to mimic the existing Egeria Java Client structure.
+
+The commands folder holds the Egeria Command Line Interface and corresponding commands
+to visualize and use Egeria. The commands also serve as useful examples.
+
+An examples folder holds some useful examples showing different facets of using pyegeria.
+
+For detailed guidance on report formats (selection and migration from columns→attributes), see:
+- examples/doc_samples/report_formats.md
+
+### Report specs: families and filtering
+
+Report specs (aka format sets) can be tagged with an optional `family` string to help organize and discover related specs.
+
+- Show names with family and sort by family, then name:
+
+```python
+from pyegeria.base_report_formats import report_spec_list
+
+names = report_spec_list(show_family=True, sort_by_family=True)
+for n in names:
+    print(n)
+```
+
+- Filter specs by family programmatically:
+
+```python
+from pyegeria.base_report_formats import report_specs
+
+# Exact family match (case-insensitive)
+security_specs = report_specs.filter_by_family("Security")
+# Specs with no family assigned
+no_family_specs = report_specs.filter_by_family("")
+```
+
+WARNING: files that start with "X" are in-progress placeholders that are not meant to be used..they will mature and 
+evolve.
+
+All feedback is welcome. Please engage via our [community](http://egeria-project.org/guides/community/), 
+team calls, or via github issues in this repo. If interested in contributing,
+you can engage via the community or directly reach out to
+[dan.wolfson\@pdr-associates.com](mailto:dan.wolfson@pdr-associates.com?subject=pyegeria).
+
+This is a learning experience.
+
+## Configuration
+
+pyegeria uses a simple, predictable precedence for configuration:
+
+1. Built-in defaults (Pydantic models in pyegeria.config)
+2. Config file (JSON) if found
+3. Environment variables (OS env and optional .env)
+4. Explicit env file passed to get_app_config/load_app_config
+
+Environment always overrides config file, which overrides defaults.
+
+### Where to put your configuration
+
+- Config file: A JSON file named config.json. The loader looks in this order:
+  - If PYEGERIA_CONFIG_DIRECTORY is set: $PYEGERIA_CONFIG_DIRECTORY/$PYEGERIA_CONFIG_FILE
+  - Else if PYEGERIA_ROOT_PATH is set: $PYEGERIA_ROOT_PATH/$PYEGERIA_CONFIG_FILE
+  - Else: ./config.json (the current working directory)
+
+- .env file: Optional. If present in the current working directory (.env), variables from it will be loaded. You can also pass a specific env file path to get_app_config(env_file=...) or load_app_config(env_file=...). For sample variables, see config/env in this repo.
+
+### Common environment variables
+
+- PYEGERIA_CONFIG_DIRECTORY: directory containing your config.json
+- PYEGERIA_ROOT_PATH: root folder used to resolve config.json when CONFIG_DIRECTORY is not set
+- PYEGERIA_CONFIG_FILE: filename of the configuration JSON (default: config.json)
+- PYEGERIA_CONSOLE_WIDTH: integer console width (e.g., 200 or 280)
+- EGERIA_PLATFORM_URL, EGERIA_VIEW_SERVER_URL, EGERIA_ENGINE_HOST_URL: URLs for your Egeria servers
+- EGERIA_USER, EGERIA_USER_PASSWORD: credentials used by some clients
+- Logging related: PYEGERIA_ENABLE_LOGGING, PYEGERIA_LOG_DIRECTORY, PYEGERIA_CONSOLE_LOG_LVL, PYEGERIA_FILE_LOG_LVL, etc.
+
+See config/env for more variables and defaults.
+
+### Example .env
+
+# PYEGERIA_CONFIG_DIRECTORY=/path/to/configs
+# PYEGERIA_ROOT_PATH=/path/to/project
+# PYEGERIA_CONFIG_FILE=config.json
+# EGERIA_PLATFORM_URL=https://localhost:9443
+# EGERIA_VIEW_SERVER=qs-view-server
+# EGERIA_VIEW_SERVER_URL=https://localhost:9443
+# EGERIA_USER=myuser
+# EGERIA_USER_PASSWORD=mypassword
+# PYEGERIA_CONSOLE_WIDTH=280
+
+Lines starting with # are comments. Quotes are optional; python-dotenv/pydantic-settings handle both.
+
+### Example config.json (minimal)
+
+{
+  "Environment": {
+    "Pyegeria Root": ".",
+    "Egeria Platform URL": "https://localhost:9443"
+  },
+  "User Profile": {
+    "Egeria Home Collection": "MyHome"
+  }
+}
+
+### Programmatic usage
+
+from pyegeria import get_app_config
+cfg = get_app_config()  # uses OS env and ./.env
+# or with explicit env file
+cfg = get_app_config(env_file="/path/to/dev.env")
+
+# Access values via Pydantic models
+print(cfg.Environment.egeria_platform_url)
+print(cfg.Logging.enable_logging)
+
+### CLI quick checks
+
+- Validate your env file:
+  python scripts/validate_env.py --env config/env
+  python scripts/validate_env.py               # auto-detects ./config/env or ./.env
+
+### Testing
+
+By default, running pytest executes unit tests that use monkeypatching/fakes and do not contact a live Egeria.
+
+- Run unit tests (recommended default):
+  poetry install
+  poetry run pytest -v
+
+You can also run tests live against a local Egeria instance. Enable live mode with either a CLI flag or an environment variable. In live mode, tests marked as `unit` are skipped and live tests run using a real Client2 connection.
+
+- Enable live mode via CLI:
+  poetry run pytest -q --live-egeria
+
+- Or enable via environment variable:
+  PYEG_LIVE_EGERIA=1 poetry run pytest -q
+
+Default live connection parameters (can be overridden via env):
+- server_name = "qs-view-server"           (override with PYEG_SERVER_NAME)
+- platform_url = "https://localhost:9443" (override with PYEG_PLATFORM_URL)
+- user_id = "peterprofile"                (override with PYEG_USER_ID)
+- user_pwd = "secret"                      (override with PYEG_USER_PWD)
+
+Notes:
+- SSL verification is controlled by pyegeria._globals.enable_ssl_check, which defaults to False in this repo to support localhost/self-signed certs.
+- See tests/conftest.py for the live test fixtures and switches.
+
+### Troubleshooting
+
+### Troubleshooting
+
+- If your env doesn’t seem to apply, confirm which config.json is used (the loader checks PYEGERIA_CONFIG_DIRECTORY first, then PYEGERIA_ROOT_PATH, then ./config.json).
+- .env files are optional. Missing .env is not an error.
+- You can always override values with OS environment variables (they take precedence over config.json).
+
+
+
+----
+License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/),
+Copyright Contributors to the ODPi Egeria project.

pyegeria-5.4.9.5/README.md

@@ -0,0 +1,179 @@
+<!-- SPDX-License-Identifier: CC-BY-4.0 -->
+<!-- Copyright Contributors to the ODPi Egeria project. -->
+
+![Egeria Logo](https://egeria-project.org/assets/images/egeria-header.png)
+
+[![GitHub](https://img.shields.io/github/license/odpi/egeria)](LICENSE)
+
+
+# pyegeria: a python client for Egeria
+
+A lightweight Python 3.12+ client and CLI for the Egeria open metadata and governance platform. It helps you configure and operate Egeria services and work with metadata (assets, glossaries, lineage, etc.) from Python, with examples, tests, and documented report formats.
+
+This is a package for easily using the Egeria
+open metadata environment from python. Details about the
+open source Egeria project can be found at [Egeria Project](https://egeria-project.org).
+
+This package is in active development. There is initial
+support for many of Egeria's services including configuration and operation.  This client depends on 
+This release supports Egeria 5.1 - although most of the functions may work on earlier versions of Egeria as well. 
+
+The code is organized to mimic the existing Egeria Java Client structure.
+
+The commands folder holds the Egeria Command Line Interface and corresponding commands
+to visualize and use Egeria. The commands also serve as useful examples.
+
+An examples folder holds some useful examples showing different facets of using pyegeria.
+
+For detailed guidance on report formats (selection and migration from columns→attributes), see:
+- examples/doc_samples/report_formats.md
+
+### Report specs: families and filtering
+
+Report specs (aka format sets) can be tagged with an optional `family` string to help organize and discover related specs.
+
+- Show names with family and sort by family, then name:
+
+```python
+from pyegeria.base_report_formats import report_spec_list
+
+names = report_spec_list(show_family=True, sort_by_family=True)
+for n in names:
+    print(n)
+```
+
+- Filter specs by family programmatically:
+
+```python
+from pyegeria.base_report_formats import report_specs
+
+# Exact family match (case-insensitive)
+security_specs = report_specs.filter_by_family("Security")
+# Specs with no family assigned
+no_family_specs = report_specs.filter_by_family("")
+```
+
+WARNING: files that start with "X" are in-progress placeholders that are not meant to be used..they will mature and 
+evolve.
+
+All feedback is welcome. Please engage via our [community](http://egeria-project.org/guides/community/), 
+team calls, or via github issues in this repo. If interested in contributing,
+you can engage via the community or directly reach out to
+[dan.wolfson\@pdr-associates.com](mailto:dan.wolfson@pdr-associates.com?subject=pyegeria).
+
+This is a learning experience.
+
+## Configuration
+
+pyegeria uses a simple, predictable precedence for configuration:
+
+1. Built-in defaults (Pydantic models in pyegeria.config)
+2. Config file (JSON) if found
+3. Environment variables (OS env and optional .env)
+4. Explicit env file passed to get_app_config/load_app_config
+
+Environment always overrides config file, which overrides defaults.
+
+### Where to put your configuration
+
+- Config file: A JSON file named config.json. The loader looks in this order:
+  - If PYEGERIA_CONFIG_DIRECTORY is set: $PYEGERIA_CONFIG_DIRECTORY/$PYEGERIA_CONFIG_FILE
+  - Else if PYEGERIA_ROOT_PATH is set: $PYEGERIA_ROOT_PATH/$PYEGERIA_CONFIG_FILE
+  - Else: ./config.json (the current working directory)
+
+- .env file: Optional. If present in the current working directory (.env), variables from it will be loaded. You can also pass a specific env file path to get_app_config(env_file=...) or load_app_config(env_file=...). For sample variables, see config/env in this repo.
+
+### Common environment variables
+
+- PYEGERIA_CONFIG_DIRECTORY: directory containing your config.json
+- PYEGERIA_ROOT_PATH: root folder used to resolve config.json when CONFIG_DIRECTORY is not set
+- PYEGERIA_CONFIG_FILE: filename of the configuration JSON (default: config.json)
+- PYEGERIA_CONSOLE_WIDTH: integer console width (e.g., 200 or 280)
+- EGERIA_PLATFORM_URL, EGERIA_VIEW_SERVER_URL, EGERIA_ENGINE_HOST_URL: URLs for your Egeria servers
+- EGERIA_USER, EGERIA_USER_PASSWORD: credentials used by some clients
+- Logging related: PYEGERIA_ENABLE_LOGGING, PYEGERIA_LOG_DIRECTORY, PYEGERIA_CONSOLE_LOG_LVL, PYEGERIA_FILE_LOG_LVL, etc.
+
+See config/env for more variables and defaults.
+
+### Example .env
+
+# PYEGERIA_CONFIG_DIRECTORY=/path/to/configs
+# PYEGERIA_ROOT_PATH=/path/to/project
+# PYEGERIA_CONFIG_FILE=config.json
+# EGERIA_PLATFORM_URL=https://localhost:9443
+# EGERIA_VIEW_SERVER=qs-view-server
+# EGERIA_VIEW_SERVER_URL=https://localhost:9443
+# EGERIA_USER=myuser
+# EGERIA_USER_PASSWORD=mypassword
+# PYEGERIA_CONSOLE_WIDTH=280
+
+Lines starting with # are comments. Quotes are optional; python-dotenv/pydantic-settings handle both.
+
+### Example config.json (minimal)
+
+{
+  "Environment": {
+    "Pyegeria Root": ".",
+    "Egeria Platform URL": "https://localhost:9443"
+  },
+  "User Profile": {
+    "Egeria Home Collection": "MyHome"
+  }
+}
+
+### Programmatic usage
+
+from pyegeria import get_app_config
+cfg = get_app_config()  # uses OS env and ./.env
+# or with explicit env file
+cfg = get_app_config(env_file="/path/to/dev.env")
+
+# Access values via Pydantic models
+print(cfg.Environment.egeria_platform_url)
+print(cfg.Logging.enable_logging)
+
+### CLI quick checks
+
+- Validate your env file:
+  python scripts/validate_env.py --env config/env
+  python scripts/validate_env.py               # auto-detects ./config/env or ./.env
+
+### Testing
+
+By default, running pytest executes unit tests that use monkeypatching/fakes and do not contact a live Egeria.
+
+- Run unit tests (recommended default):
+  poetry install
+  poetry run pytest -v
+
+You can also run tests live against a local Egeria instance. Enable live mode with either a CLI flag or an environment variable. In live mode, tests marked as `unit` are skipped and live tests run using a real Client2 connection.
+
+- Enable live mode via CLI:
+  poetry run pytest -q --live-egeria
+
+- Or enable via environment variable:
+  PYEG_LIVE_EGERIA=1 poetry run pytest -q
+
+Default live connection parameters (can be overridden via env):
+- server_name = "qs-view-server"           (override with PYEG_SERVER_NAME)
+- platform_url = "https://localhost:9443" (override with PYEG_PLATFORM_URL)
+- user_id = "peterprofile"                (override with PYEG_USER_ID)
+- user_pwd = "secret"                      (override with PYEG_USER_PWD)
+
+Notes:
+- SSL verification is controlled by pyegeria._globals.enable_ssl_check, which defaults to False in this repo to support localhost/self-signed certs.
+- See tests/conftest.py for the live test fixtures and switches.
+
+### Troubleshooting
+
+### Troubleshooting
+
+- If your env doesn’t seem to apply, confirm which config.json is used (the loader checks PYEGERIA_CONFIG_DIRECTORY first, then PYEGERIA_ROOT_PATH, then ./config.json).
+- .env files are optional. Missing .env is not an error.
+- You can always override values with OS environment variables (they take precedence over config.json).
+
+
+
+----
+License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/),
+Copyright Contributors to the ODPi Egeria project.

{pyegeria-5.2.0.42.2/pyegeria → pyegeria-5.4.9.5}/commands/__init__.py

@@ -4,19 +4,27 @@ Copyright Contributors to the ODPi Egeria project.
 
 
 
-pyegeria commands available also from python.
+pyegeria md_commands available also from python.
 """
-
-from .ops.monitor_gov_eng_status import display_gov_eng_status
-from .ops.monitor_integ_daemon_status import display_integration_daemon_status
+from .cat.dr_egeria_md import process_markdown_file
+from .cat.list_deployed_catalogs import list_deployed_catalogs
+from .cat.list_deployed_database_schemas import list_deployed_database_schemas
+from .cat.list_deployed_databases import list_deployed_databases
+from .cat.list_glossaries import display_glossaries
+from .cat.list_terms import display_glossary_terms
+from .ops.list_catalog_targets import display_catalog_targets
+from .ops.monitor_engine_activity import display_engine_activity_c
+from .ops.monitor_engine_status import display_gov_eng_status
+from .ops.monitor_daemon_status import display_integration_daemon_status
 from .ops.table_integ_daemon_status import (
     display_integration_daemon_status as table_integ_daemon_status,
 )
-from .ops.monitor_engine_activity_c import display_engine_activity_c
-from .ops.list_catalog_targets import display_catalog_targets
+from .tech.list_elements_by_property_value import EGERIA_WIDTH
 
-from .cat.list_glossaries import display_glossaries
-from .cat.list_terms import display_glossary_terms
-from .cat.list_deployed_catalogs import list_deployed_catalogs
-from .cat.list_deployed_database_schemas import list_deployed_database_schemas
-from .cat.list_deployed_databases import list_deployed_databases
+
+def list_integration_daemon_status(
+    search_list: str, width: int = EGERIA_WIDTH, sort: bool = True
+):
+    table_integ_daemon_status(
+        search_list=search_list, paging=True, width=width, sort=sort
+    )

pyegeria-5.4.9.5/commands/cat/Dr-Egeria_md-orig.py

@@ -0,0 +1,166 @@
+"""
+This is an ongoing experiment in parsing and playing with Freddie docs
+"""
+import json
+import os
+from rich import print
+from rich.console import Console
+
+from pyegeria.md_processing_utils import (commands,
+                                          process_provenance_command)
+
+import click
+from pyegeria import (extract_command, process_glossary_upsert_command, process_term_upsert_command,
+                      process_category_upsert_command,
+                      get_current_datetime_string, process_per_proj_upsert_command, EgeriaTech
+                      )
+import commands
+from datetime import datetime
+
+EGERIA_METADATA_STORE = os.environ.get("EGERIA_METADATA_STORE", "active-metadata-store")
+EGERIA_KAFKA_ENDPOINT = os.environ.get("KAFKA_ENDPOINT", "localhost:9092")
+EGERIA_PLATFORM_URL = os.environ.get("EGERIA_PLATFORM_URL", "https://localhost:9443")
+EGERIA_VIEW_SERVER = os.environ.get("EGERIA_VIEW_SERVER", "view-server")
+EGERIA_VIEW_SERVER_URL = os.environ.get(
+    "EGERIA_VIEW_SERVER_URL", "https://localhost:9443"
+)
+EGERIA_INTEGRATION_DAEMON = os.environ.get("EGERIA_INTEGRATION_DAEMON", "integration-daemon")
+EGERIA_INTEGRATION_DAEMON_URL = os.environ.get(
+    "EGERIA_INTEGRATION_DAEMON_URL", "https://localhost:9443"
+)
+EGERIA_ADMIN_USER = os.environ.get("ADMIN_USER", "garygeeke")
+EGERIA_ADMIN_PASSWORD = os.environ.get("ADMIN_PASSWORD", "secret")
+EGERIA_USER = os.environ.get("EGERIA_USER", "erinoverview")
+EGERIA_USER_PASSWORD = os.environ.get("EGERIA_USER_PASSWORD", "secret")
+EGERIA_WIDTH = os.environ.get("EGERIA_WIDTH", 220)
+EGERIA_JUPYTER = os.environ.get("EGERIA_JUPYTER", False)
+EGERIA_HOME_GLOSSARY_GUID = os.environ.get("EGERIA_HOME_GLOSSARY_GUID", None)
+EGERIA_GLOSSARY_PATH = os.environ.get("EGERIA_GLOSSARY_PATH", None)
+EGERIA_ROOT_PATH = os.environ.get("EGERIA_ROOT_PATH", "../../")
+EGERIA_INBOX_PATH = os.environ.get("EGERIA_INBOX_PATH", "md_processing/dr_egeria_inbox")
+EGERIA_OUTBOX_PATH = os.environ.get("EGERIA_OUTBOX_PATH", "md_processing/dr_egeria_outbox")
+
+console = Console(width=int(EGERIA_WIDTH))
+
+
+
+@click.command("process-markdown-file", help="Process a markdown file and return the output as a string.")
+@click.option("--file-path", help="File path to markdown file",
+              default="glossary_test1.md")
+@click.option("--directive", default="display-only", help="How to process the file")
+@click.option("--server", default=EGERIA_VIEW_SERVER, help="Egeria view server to use.")
+@click.option(
+    "--url", default=EGERIA_VIEW_SERVER_URL, help="URL of Egeria platform to connect to"
+)
+@click.option("--userid", default=EGERIA_USER, help="Egeria user")
+@click.option("--user_pass", default=EGERIA_USER_PASSWORD, help="Egeria user password")
+def process_markdown_file(
+        file_path: str,
+        directive: str,
+        server: str,
+        url: str,
+        userid: str,
+        user_pass: str,
+        ):
+
+    client = EgeriaTech(server, url, user_id=userid)
+    token = client.create_egeria_bearer_token(userid, user_pass)
+
+    updated = False
+    full_file_path = os.path.join(EGERIA_ROOT_PATH, EGERIA_INBOX_PATH, file_path)
+    print(f"Processing Markdown File: {full_file_path}")
+    try:
+        with open(full_file_path, 'r') as f:
+            lines = f.readlines()
+    except FileNotFoundError:
+        print(f"Error: File not found at path: {full_file_path}")
+        return {}  # Return empty dict if file not found
+
+    final_output =""
+    prov_output = (f"\n* Results from processing file {file_path} on "
+                    f"{datetime.now().strftime("%Y-%m-%d %H:%M")}\n")
+    h1_blocks = []
+    current_block = ""
+    in_h1_block = False
+    element_dictionary = {}
+
+    for line in lines:
+        line = line.strip()  # Remove leading/trailing whitespace
+
+        if line.startswith("# ") and not in_h1_block:  # Start of a new H1 block
+            if current_block:
+                h1_blocks.append(current_block)
+            current_block = line
+            in_h1_block = True
+        elif line.startswith("---") and in_h1_block:  # End of the current H1 block
+            h1_blocks.append(current_block)
+            current_block = ""
+            in_h1_block = False
+        elif in_h1_block:  # Add line to the current H1 block
+            current_block += "\n" + line
+        else:
+            # Add non-H1 blocks directly to the final output
+            final_output += line
+
+    if current_block:  # Add the last H1 block
+        h1_blocks.append(current_block)
+    prov_found = False
+    # Process each identified H1 block
+    for block in h1_blocks:
+        potential_command = extract_command(block)  # Extract potential object_action
+
+        if potential_command in commands:
+            # Process the block based on the object_action
+            if potential_command == "Provenance":
+                prov_found = True
+                result = process_provenance_command(file_path, block)
+            elif potential_command in ["Create Glossary", "Update Glossary"]:
+                result = process_glossary_upsert_command(client, block, directive)
+            elif potential_command in ["Create Category", "Update Category"]:
+                result = process_category_upsert_command(client, block, directive)
+            elif potential_command in ["Create Term", "Update Term"]:
+                result = process_term_upsert_command(client, block, directive)
+            elif potential_command in ["Create Personal Project", "Update Personal Project"]:
+                result = process_per_proj_upsert_command(client, block, directive)
+            else:
+                # If object_action is not recognized, copy the block as-is
+                result = None
+
+            if result:
+                if directive == "process":
+                    updated = True
+                    final_output += f"\n---\n{result}\n"
+                    print(json.dumps(element_dictionary, indent=4))
+            elif directive == "process":
+                # Handle case with errors (skip this block but notify the user)
+                print(f"\n==>\tErrors found while processing command: \'{potential_command}\'\n"
+                      f"\tPlease correct and try again. \n")
+                final_output += f"\n---\n{block}\n"
+        else:
+            # If no object_action is detected, add the block to the final output as-is
+            final_output += f"\n---\n{block}\n"
+
+
+    # Write the final_output to a new file if updated
+    try:
+        if updated:
+            path, filename = os.path.split(file_path)  # Get both parts
+            new_filename = f"processed-{get_current_datetime_string()}-{filename}"  # Create the new filename
+            new_file_path = os.path.join(EGERIA_ROOT_PATH, EGERIA_OUTBOX_PATH, new_filename)  # Construct the new path
+            os.makedirs(os.path.dirname(new_file_path), exist_ok=True)
+
+            with open(new_file_path, 'w') as f2:
+                f2.write(final_output)
+                if not prov_found:
+                    prov_output += f"\n# Provenance:\n{prov_output}\n"
+                f2.write(prov_output)
+            click.echo(f"\n==> Notebook written to {new_file_path}")
+        else:
+            click.echo("\nNo updates detected. New File not created.")
+
+    except (Exception):
+        console.print_exception(show_locals=True)
+
+
+if __name__ == "__main__":
+    process_markdown_file()

pyegeria-5.4.9.5/commands/cat/__init__.py

@@ -0,0 +1,7 @@
+"""
+SPDX-License-Identifier: Apache-2.0
+Copyright Contributors to the ODPi Egeria project.
+"""
+
+
+