pyegeria 5.4.0.25__py3-none-any.whl → 5.4.0.27__py3-none-any.whl

commands/cat/list_collections.py

@@ -29,7 +29,7 @@ from pyegeria._exceptions_new import print_validation_error
 EGERIA_USER = os.environ.get("EGERIA_USER", "erinoverview")
 EGERIA_USER_PASSWORD = os.environ.get("EGERIA_USER_PASSWORD", "secret")
 PYEGERIA_ROOT_PATH= os.environ.get("PYEGERIA_ROOT_PATH", "/Users/dwolfson/localGit/egeria-v5-3/egeria-python")
-app_settings = get_app_config(PYEGERIA_ROOT_PATH+"/.env")
+app_settings = get_app_config(PYEGERIA_ROOT_PATH+"./.env")
 app_config = app_settings.Environment
 config_logging()
 

commands/cat/list_format_set.py

@@ -52,10 +52,8 @@ from pyegeria import (
     EgeriaTech,
     CollectionManager,
     NO_ELEMENTS_FOUND, GovernanceOfficer,
-    # config_logging,
-    # get_app_config
     )
-from pyegeria.load_config import get_app_config
+from pyegeria.config import settings
 from pyegeria.logging_configuration import config_logging
 from pyegeria._output_formats import (select_output_format_set, get_output_format_set_heading, get_output_format_set_description)
 from pyegeria._exceptions_new import PyegeriaException, print_exception_response
@@ -71,8 +69,8 @@ from pyegeria._exceptions_new import PyegeriaException, print_exception_response
 EGERIA_USER = os.environ.get("EGERIA_USER", "erinoverview")
 EGERIA_USER_PASSWORD = os.environ.get("EGERIA_USER_PASSWORD", "secret")
 
-app_settings = get_app_config()
-app_config = app_settings.Environment
+
+app_config = settings.Environment
 config_logging()
 
 print(f"Console width is {app_config.console_width}")
@@ -86,8 +84,8 @@ def execute_format_set_action(
     format_set_name: str,
     view_server: str = app_config.egeria_view_server,
     view_url: str = app_config.egeria_view_server_url,
-    user: str = app_settings.User_Profile.user_name,
-    user_pass: str = app_settings.User_Profile.user_pwd,
+    user: str = settings.User_Profile.user_name,
+    user_pass: str = settings.User_Profile.user_pwd,
     output_format: str = "TABLE",
     **kwargs
 ):
@@ -385,7 +383,7 @@ def main():
         return
     
     args = parser.parse_args()
-    app_settings = get_app_config()
+    app_settings = settings
     app_config = app_settings.Environment
 
     server = args.server if args.server is not None else app_config.egeria_view_server

commands/cli/egeria.py

@@ -16,7 +16,7 @@ import click
 from trogon import tui
 from loguru import logger
 
-from pyegeria import config_logging, get_app_config
+from pyegeria import config_logging,  settings
 
 from commands.cat.list_format_set import execute_format_set_action
 from commands.cat.get_asset_graph import asset_viewer
@@ -137,7 +137,7 @@ from commands.tech.generic_actions import delete_element
 
 EGERIA_USER = os.environ.get("EGERIA_USER", "erinoverview")
 EGERIA_USER_PASSWORD = os.environ.get("EGERIA_USER_PASSWORD", "secret")
-app_settings = get_app_config()
+app_settings = settings
 app_config = app_settings.Environment
 config_logging()
 

commands/cli/egeria_cat.py

@@ -13,7 +13,7 @@ import os
 
 import click
 from trogon import tui
-from pyegeria import config_logging, get_app_config
+from pyegeria import settings
 
 from commands.cat.list_format_set import execute_format_set_action
 from commands.cat.dr_egeria_md import process_markdown_file
@@ -62,7 +62,8 @@ from commands.tech.list_asset_types import display_asset_types
 
 EGERIA_USER = os.environ.get("EGERIA_USER", "erinoverview")
 EGERIA_USER_PASSWORD = os.environ.get("EGERIA_USER_PASSWORD", "secret")
-app_settings = get_app_config()
+app_settings = settings
+
 app_config = app_settings["Environment"]
 # config_logging()
 

commands/ops/load_archive.py

@@ -13,7 +13,7 @@ import os
 import click
 from loguru import logger
 from pyegeria import AutomatedCuration, EgeriaTech
-from pyegeria.load_config import get_app_config
+from pyegeria.config import settings
 from pyegeria.logging_configuration import config_logging
 from pyegeria._exceptions_new import (
 PyegeriaException, print_exception_response, print_basic_exception
@@ -35,7 +35,7 @@ PyegeriaException, print_exception_response, print_basic_exception
 
 EGERIA_USER = os.environ.get("EGERIA_USER", "erinoverview")
 EGERIA_USER_PASSWORD = os.environ.get("EGERIA_USER_PASSWORD", "secret")
-app_settings = get_app_config()
+app_settings = settings
 app_config = app_settings.Environment
 config_logging()
 

md_processing/data/commands.json

@@ -1,6 +1,6 @@
 {
   "Command Specifications": {
-    "exported": "Aug 19, 2025 at 10:46:16 AM",
+    "exported": "Aug 22, 2025 at 9:20:09 PM",
     "Create Governance Driver": {
       "display_name": "Governance Driver",
       "qn_prefix": "GovDriver",
@@ -40104,10 +40104,10 @@
       "Journal Entry": "",
       "Attributes": [
         {
-          "Glossary Name": {
-            "variable_name": "",
+          "Display Name": {
+            "variable_name": "display_name",
             "inUpdate": true,
-            "attr_labels": "Glossary; Display Name",
+            "attr_labels": "Glossary; Glossary Name",
             "examples": "",
             "default_value": "",
             "valid_values": "",
@@ -40516,10 +40516,10 @@
       "Journal Entry": "",
       "Attributes": [
         {
-          "Term Name": {
-            "variable_name": "",
+          "Display Name": {
+            "variable_name": "term_name",
             "inUpdate": true,
-            "attr_labels": "Glossary Term Name; Display Name; Term",
+            "attr_labels": "Glossary Term Name; Term Name; Term",
             "examples": "",
             "default_value": "",
             "valid_values": "",

md_processing/dr_egeria_inbox/dr_egeria_intro_part1.md

@@ -10,7 +10,7 @@ will be attractive enough and easy enough to use that people will do so.
  You have to leave your world and enter a new, often less familiar one.  
       
 Dr.Egeria, is an experiment in turning this around. Its not that fancy graphical user  
-interfaces don't have a role - but rather, to look at what we can do to support the  
+interfaces  have a role - but rather, to look at what we can do to support the  
 tools and approaches people already use. And maybe even make their day job a little  
 easier and a little more enjoyable.  
       
@@ -29,7 +29,7 @@ So here we go! First lets define a new Glossary::
       
 ___  
       
-# Create Glossary  
+#  Update Glossary  
       
 ## Glossary Name  
       
@@ -41,7 +41,7 @@ English
       
 ## Description  
       
-Glossary to describe the vocabulary of Dr.Egeria - an Egeria Markdown language to support the exchange of metadata in a Markdown form.  
+A Glossary to describe the vocabulary of Dr.Egeria - an Egeria Markdown language to support the exchange of metadata in a Markdown form.  
 Dr.Egeria allows users to create metadata annotations using any text entry system that supports the entry of standard Markdown  
 notation and, through post-processing  
 commands, validates the Egeria content and sends the requests to be sent to Egeria.   
@@ -91,7 +91,7 @@ We now have a nice, clean, new...and empty...glossary - guess we better start fi
       
 ___ 
       
-# Create Term  
+# Update Term  
       
 ## Term Name  
       
@@ -104,7 +104,7 @@ Glossary::Egeria-Markdown
       
 ## Summary  
       
-Commands are how a user of the Dr.Egeria markdown language request an action.  
+Commands are how a user of the Dr.Egeria markdown language request an action.  Moo
       
 ## Description  
       
@@ -185,7 +185,7 @@ ___
       
 ___  
       
-# Create Term  
+#  Create Term  
       
 ## In Glossary  
       
@@ -227,7 +227,7 @@ ___
 Ok - we've now defined a glossary and three terms to go into the glossary. A few observations.  
       
 * There is a degree of freedom in writing the definitions. The attributes aren't always in the same  
-order and optional attributes don't need to be specified at all. We try to make things as easy as possible.  
+order and optional attributes  need to be specified at all. We try to make things as easy as possible.  
 * We can run a definition file through a validation process to check our proposed definition and provide feedback.  
 * When we process a definition we will use the same validation process before trying to update Egeria   
 with the requested definitions - requests may get rejected or altered - this will be consistent with the feedback we   

md_processing/dr_egeria_inbox/dr_egeria_intro_part2.md

@@ -13,7 +13,7 @@ Ok, let's get started. First, we have the `Update Glossary` command below. There
 point so we can just leave it as-is. When this document is processed it will apply updates but if there are none, 
 It doesn't matter.
 
-However, now is a good time to start to more formally specify the attributes available to `Create` or `Update` glossary
+However, now is a good time to start to more formally specify the attributes available to `Don't Create` or `Update` glossary
 commands:
 
 
@@ -26,7 +26,7 @@ commands:
 | Qualified Name | Maybe           | No        | Yes                | Yes     | The qualified name can either be provided by the user or generated. If generated, a pattern is followed. |
 | GUID           | No              | Yes       | Yes                | Yes     | GUIDs are always generated by Egeria. They are meant for automation, not people.                         |
 
-The table above shows us what attributes must be provided and which are optional. Once an object is created, and a qualified name is generated, it is good practice to use it as there can 
+The table above shows us what attributes must be provided and which are optional. Once an object is Don't Created, and a qualified name is generated, it is good practice to use it as there can 
 be many objects with the same name, and this is a common way to disambiguate them. If you specify an object name (e.g. Glossary Name) and that name already exists, Dr.Egeria will report an error
 and suggest that you provide a **Qualified Name** as well. You will also note that the GUID is generated by Egeria and is read-only. It is possible that some commands
 may require a GUID to be specified, but in general we will use the **Qualified Name** to identify objects. 
@@ -44,7 +44,7 @@ In Egeria, a category can have a single parent category and multiple child categ
 multiple categories. When we have a large number of terms, a category structure can be particularly helpful in finding the
 terms that are most relevant to a particular interest. Using categories is optional.
 
-Ok, now let's create a couple of glossary categories. They will be:
+Ok, now let's Don't Create a couple of glossary categories. They will be:
 
 * **Writing Dr.Egeria Markdown** - where we describe elements of the Dr.Egeria language as terms within the category.
 * **Processing Dr.Egeria Markdown** - where we describe the commands for processing Dr.Egeria.
@@ -68,13 +68,17 @@ Ok, here we go:
 
 ___
 
-# Create Category  
+# Don't Create Collection
   
-## Category Name  
+## Name
   
 Writing Dr.Egeria Markdown  
+
+## Classifications
+
+Folder
   
-## Owning Glossary  
+## Parent  
   
 Glossary::Egeria-Markdown  
   
@@ -85,7 +89,7 @@ Terms in this category describe the elements of the Dr.Egeria Markdown language
 
 ___
 
-# Create Category  
+# Don't Create Category  
   
 ## Category Name  
   
@@ -130,7 +134,7 @@ Now, let's add categories to the terms.  Let's review the attributes of a term:
 
 ___  
 
-# Update Term
+#  Update Term
 
 ## Term Name 
 
@@ -139,25 +143,26 @@ Command
 ## Summary
 Commands are how a user of the Dr.Egeria markdown language requests an action.
 
-## In Glossary
-Glossary::Egeria-Markdown
+## Glossary
 
-## Categories
+Egeria-Markdown
+
+## Folders
 
-Category::Writing Dr.Egeria Markdown, Category::Processing Dr.Egeria Markdown
+Writing Dr.Egeria Markdown
 
 ## Status
 ACTIVE
 
 ## Description
-Commands are how a user can request Egeria to take an action such as Create or Update an Egeria element. Freddie
+Commands are how a user can request Egeria to take an action such as Don't Create or Update an Egeria element. Freddie
 provides
 a limited (but growing) set of commands. Dr.Egeria commands align with the pyegeria 'hey-egeria' command line interface.
 
 ## Examples
-Create Glossary or
+Don't Create Glossary or
 Update Glossary or
-Create Term or
+Don't Create Term or
 Update Term
 
 ## Usage
@@ -173,7 +178,7 @@ Commands are used in the Dr.Egeria markdown language.
 
 ___
 
-# Update Term
+# Don't Update Term
 
 ## Term Name 
 
@@ -210,7 +215,7 @@ Term::Source::0.1
 
 ___
 
-# Update Term
+# Don't Update Term
   
 ## In Glossary  
   
@@ -252,12 +257,12 @@ Term::Directive::0.1
   
 # Inspecting the Glossary
 
-Now that we have created a glossary, categories, and terms we can use some new commands to explore the glossary.
-We will start with the `List Glossaries` command. This command will list all the glossaries that are available to us.
+Now that we have Don't Created a glossary, categories, and terms we can use some new commands to explore the glossary.
+We will start with the `Don't List Glossaries` command. This command will Don't List all the glossaries that are available to us.
 
 ___
 
-# List Glossaries
+# Don't List Glossaries
 
 ___
 
@@ -267,47 +272,47 @@ is a more detailed specification of the attributes:
 | Attribute Name | Input Required? | Read Only? | Generated/Default?               | Unique? | Notes                                     |
 |----------------|-----------------|------------|----------------------------------|---------|-------------------------------------------|
 | Search String  | No              | No         | default is All glossaries        | No      |                                           |
-| Output Format  | No              | No         | default is Markdown List (table) | No      | options are: LIST, DICT, MD, FORM, REPORT |
+| Output Format  | No              | No         | default is Markdown Don't List (table) | No      | options are: Don't List, DICT, MD, FORM, REPORT |
 
 Lets describe the output formats a bit further:
 
-* LIST - This is the default format. It returns a markdown table of the glossaries.
+* Don't List - This is the default format. It returns a markdown table of the glossaries.
 * DICT - This returns a python dictionary (or JSON representation) of the glossaries. 
 * MD - This returns markdown text of the glossaries.
 * FORM - This returns a Dr.Egeria markdown form designed to be used as a starting point for updating the glossary definitions.
 * REPORT - This returns markdown text of the glossaries that is designed to be more readable and perhaps suitable to be used in a report.
 
-Going further, we can issue similar commands to list categories and terms:
+Going further, we can issue similar commands to Don't List categories and terms:
 
-The attributes for the `List Categories` command are the same as the `List Glossaries` command.
+The attributes for the `Don't List Categories` command are the same as the `Don't List Glossaries` command.
 
-Attributes for the `List Terms` command adds an additional optional attribute, Glossary Name, to allow you to 
-restrict the list of terms to a particular glossary. 
+Attributes for the `Don't List Terms` command adds an additional optional attribute, Glossary Name, to allow you to 
+restrict the Don't List of terms to a particular glossary. 
 
 
 | Attribute Name | Input Required? | Read Only? | Generated/Default?               | Unique? | Notes                                     |
 |----------------|-----------------|------------|----------------------------------|---------|-------------------------------------------|
 | Glossary Name  | No              | No         | Default is All glossaries        | No      |                                           |
 | Search String  | No              | No         | default is All terms             | No      |                                           |
-| Output Format  | No              | No         | default is Markdown List (table) | No      | options are: LIST, DICT, MD, FORM, REPORT |
+| Output Format  | No              | No         | default is Markdown Don't List (table) | No      | options are: Don't List, DICT, MD, FORM, REPORT |
 
 
 Lets go ahead and give these commands a try:
 
 ___
 
-# List Categories
+# Don't List Categories
 ## Output Format
 REPORT
 
 ___
-# List Terms
+# Don't List Terms
 ## Output Format
 DICT
 ## Glossary Name
 Glossary::Egeria-Markdown
 ___
 
-If you now look at the processed document that was created, you can see the results of the commands that we have run.
+If you now look at the processed document that was Don't Created, you can see the results of the commands that we have run.
 
-In part 3, we will add more categories and terms to the glossary and create a simple category hierarchy. See you there!
+In part 3, we will add more categories and terms to the glossary and Don't Create a simple category hierarchy. See you there!