eclipse-tractusx / ssi-credential-issuer

SSI Credential Issuer
Apache License 2.0
4 stars 10 forks source link

QG checks (Release 24.12) #303

Closed evegufy closed 5 days ago

evegufy commented 2 weeks ago

QG checks

Please open and fill in this issue in your product repository to document the compliance with our Tractus-X Release Guideline (TRGs)

Show compliance with TRGs by referencing to a tagged link in the respective repository where possible, example: TRG 1.01 (see github.com/eclipse-tractusx/example-repo/tree/1.0.0/README.md)

Close this issue once the compliance with the TRGs has been documented

Committer(s): @Phil91 @evegufy @ntruchsess Helm Chart Version: 1.2.0 App Version: 1.2.0

Release Management Reference Issue: https://github.com/eclipse-tractusx/sig-release/issues/921

Check of Tractus-X Release Guidelines

TRG 1 Documentation

TRG 2 Git

TRG 3 Kubernetes

TRG 4 Container

TRG 5 Helm

TRG 6 Released Helm Chart

TRG 7 Open Source Governance

TRG 8 Security

TRG 9 UX/UI Styleguide

Hints

Information Sharing

evegufy commented 1 week ago

example from previous release https://github.com/eclipse-tractusx/ssi-credential-issuer/issues/223

dhiren-singh-007 commented 1 week ago

TRG 1 Documentation

TRG 2 Git

TRG 3 Kubernetes

TRG 4 Container

TRG 5 Helm

TRG 6 Released Helm Chart

TRG 7 Open Source Governance

TRG 8 Security

Hints

Information Sharing

evegufy commented 5 days ago

Hi @dhiren-singh-007 it's great that you get to know the Tractus-X Release guidelines!

In the following some explanation for the TRG's which aren't check boxed yet:

Please see final version https://github.com/eclipse-tractusx/ssi-credential-issuer/blob/v1.2.0/CHANGELOG.md

Please see final version https://github.com/eclipse-tractusx/ssi-credential-issuer/tree/v1.2.0/docs/admin

N/A due to the nature of the product.

Please see final version https://github.com/eclipse-tractusx/ssi-credential-issuer/tree/v1.2.0/docs/api

  • [x] TRG 3.02 persistent volume and persistent volume claim or database dependency (subchart) are in place when needed

The chart has a db subchart in place which manages the persistence https://github.com/eclipse-tractusx/ssi-credential-issuer/blob/v1.2.0/charts/ssi-credential-issuer/Chart.yaml#L27

  • [x] TRG 5.02 Helm chart location in /charts directory and correct structure

helmignore file is available https://github.com/eclipse-tractusx/ssi-credential-issuer/blob/v1.2.0/charts/ssi-credential-issuer/.helmignore but adding values?.yaml values?.yml wouldn't make sense as we don't maintain any such file in the charts directory. Example for when such an entry makes sense: https://github.com/eclipse-tractusx/sd-factory/tree/v2.1.14/charts/sdfactory

  • [x] TRG 7.03 IP checks for project content <!-- for each PR containing more than 1000 relevant lines there must be an approved [IP review for Code Contributions]

Here you should try to understand what the dependencies check does https://github.com/eclipse-tractusx/ssi-credential-issuer/blob/v1.2.0/.github/workflows/dependencies.yml and check if it rans without any error on the tag. In addition you should familiarise yourself with the Eclipse Dash Tool, and execute the Eclipse Dash Tool commands in the workflow locally to make sure that no dependencies restricted, see https://github.com/eclipse-tractusx/ssi-credential-issuer/blob/v1.2.0/DEPENDENCIES

  • [x] TRG 7.04 IP checks for 3rd party content

In this repository there are no examples of such 3rd party content, but you should still be familiar with the content of the TRG

  • [x] TRG 7.06 Legal information for end user content

The repository doesn't include a frontend component, therefore N/A.

evegufy commented 5 days ago

Regarding

Yes, right, in order to check this, you'd need access to the security tab of the repo, which requires maintenance/committer permissions. I check it's all fine.

The same applies also to the following TRGs:

TRG 8 Security

  • [x] TRG 8.01 Mitigate high and above findings in CodeQL
  • [x] TRG 8.02 Mitigate high and above findings in KICS
  • [x] TRG 8.04 Mitigate high and above findings in Trivy
  • [x] TRG 8.03 No secret findings by GitGuardian or TruffleHog

Checking the workflow, especially the runs is good, but constantly monitoring the security tab and making sure that security alerts are managed, is also the responsibly of a committer.