-
David Diederich authored
The schema-reference module was removed from the code with 1c31709a, but the fossa configuration was missed. As a result, the fossa-analyze steps were failing, unable to list dependencies in the non-existent project.
David Diederich authoredThe schema-reference module was removed from the code with 1c31709a, but the fossa configuration was missed. As a result, the fossa-analyze steps were failing, unable to list dependencies in the non-existent project.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
.fossa.yml 1.19 KiB
# Generated by FOSSA CLI (https://github.com/fossas/fossa-cli)
# Visit https://fossa.com to learn more
version: 2
cli:
server: https://app.fossa.com
fetcher: custom
project: Schema
analyze:
modules:
- name: os-schema
type: mvn
target: pom.xml
path: .
- name: os-schema-core
type: mvn
target: schema-core/pom.xml
path: .
- name: os-schema-aws
type: mvn
target: provider/schema-aws/pom.xml
path: .
- name: os-schema-gcp
type: mvn
target: provider/schema-gcp/pom.xml
path: .
- name: os-schema-ibm
type: mvn
target: provider/schema-ibm/pom.xml
path: .
- name: os-schema-azure
type: mvn
target: provider/schema-azure/pom.xml
path: .
- name: google
type: pip
target: deployments/scripts/google
path: deployments/scripts/google
- name: ibm
type: pip
target: deployments/scripts/ibm
path: deployments/scripts/ibm
- name: scripts
type: pip
target: deployments/scripts
path: deployments/scripts
- name: aws
type: pip
target: deployments/scripts/aws
path: deployments/scripts/aws
- name: azure
type: pip
target: deployments/scripts/azure
path: deployments/scripts/azure