Skip OpenAPI generation during FOSSA Analysis

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

• NO

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this introduce a breaking change?

• NO

What is the current behavior?

fossa-analyze fails because the committed openapi.yaml file can be changed by the build. This creates a dirty repository, which generates an invalid revisions hash and breaks the FOSSA API.

It was fixed with version 0.10 of divido/fossa-with-cache>, but that version hasn't been deployed to the standard osdu/platform/ci-cd-pipelines> yet. This quick fix bypasses the problem by not generating this file within the fossa-analyze job.

What is the new/expected behavior?

The openapi.yaml file is not generated during the fossa-analyze stage.

Have you added/updated Unit Tests and Integration Tests?

None applicable

Any other useful information