Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Extend information from leapp saved to leappdb #847

Merged
merged 4 commits into from
May 13, 2024
Merged

Extend information from leapp saved to leappdb #847

merged 4 commits into from
May 13, 2024

Commits on May 10, 2024

  1. Extend leappdb for leapp-inspector 

    This commit combines multiple additions to the leapp database.

First addition is tracking of entity metadata. The `Metadata` model
stores the metadata of entities such as `Actor` or `Workflow`. This data
is stored in a new table `metadata` of the `leapp.db` file.

  1. metadata of *discovered* actors.

     For an actor, the metadata stored contain:

	`class_name` 	- the name of the actor class
	`name`		- the name given to the actor
	`description`	- the actor's description
	`phase` 	- phase of execution of the actor
	`tags`		- names of any tags associated with an actor
	`consumes` 	- list of all messages the actor consumes
	`produces`	- list of all messages the actor produces
	`path`		- the path to the actor source file

  2. workflow metadata.

     For a workflow, the metadata stored contain:

       `name`		- name of the workflow
       `short_name` 	- short name of the workflow
       `tag`		- workflow tag
       `description`	- workflow description
       `phases` 	- all phases associated with the workflow

Next addition is tracking of dialog question. Previously leapp was not
able to detect the actual question asked from the user as it could be
generated dynamically when actor is called and depend on the
configuration of the user's system.

Last addition includes storing the actor exit status. Exit status is now
saved as an audit event `actor-exit-status`. Exit status 0 represents
successful execution or `StopActorExecution`/`StopActorExecutionError`,
while 1 indicates an unexpected and unhandled exception.

These changes collectively improve the metadata handling capabilities
of, ensuring accurate storage and retrieval of essential information for
various entities.
    @dkubek @pirat89
    dkubek authored and pirat89 committed May 10, 2024
    Configuration menu
    Copy the full SHA
    c47ac2f View commit details
    Browse the repository at this point in the history

  2. Modify clone_context for new tables

    @dkubek @pirat89
    dkubek authored and pirat89 committed May 10, 2024
    Configuration menu
    Copy the full SHA
    9c4f5a7 View commit details
    Browse the repository at this point in the history

  3. Split metadata data

    @dkubek @pirat89
    dkubek authored and pirat89 committed May 10, 2024
    Configuration menu
    Copy the full SHA
    4fa2910 View commit details
    Browse the repository at this point in the history

  4. fixup! Split metadata data

    @pirat89
    pirat89 committed May 10, 2024
    Configuration menu
    Copy the full SHA
    944b729 View commit details
    Browse the repository at this point in the history