Skip to content

Certain properties from the packit PS module object require multi-string values, very error prone #2

Description

@nicu-caphyon

The LLM could not generate a script that builds a packit fragment because our docs are not suficient and the current properties requires values which are not really well designed. For example, for:

Set-PacKitDetectionRule `

    -Fragment $fragment `

    -Format 'Use a custom detection script' `

    -Type 'PowerShell' `

    -ScriptPath $detectionScriptPath

The Format and Type are identical to our GUI values, not very friendly for a script. Type I would argue is uselles when setting a script, since we only support PowerShell. The same for properties requiring OS arch, it should be x64 not "64-bit", etc...

Full sample in:

Z:\caphyon-users\bogdan\PacKit\PacKit PS Module - demo\create-packit-fragment-demo.ps1

Other then these issue and the fact the module is not yet in the PS gallery, the LLM generated a usable script.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions