Skip to content

Does the appVersion field make sense in hook-Charts? #1959

@o1oo11oo

Description

@o1oo11oo

📚 Documentation Issue

Where to find the issue

The documentation for integrating a hook suggests to add both the version and appVersion to Chart.yaml and set both of them to latest. Now from what I remember we didn't want to use latest anywhere, so when integrating the persistence-dependencytrack hook I took inspiration from the DefectDojo and Elastic hooks and set the version to some existing SCB version and the appVersion to the latest version of Dependency-Track at that time.

Describe the issue

The helm chart doesn't really package Dependency-Track but the hook to interact with it, which isn't versioned individually from the SCB anyway. At this point most of these values in our hooks are kind of meaningless.

Suggested change

@J12934 suggested in #1854 that we could also remove the appVersion because it is an optional field. Or we could clearly specify in the docs what we use it for, for example, lowest version of the app we tested against. Then we'd have to keep these tests going against that version or raise it accordingly though.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions