fix(opportunities): add fieldValue (preferred) + deprecate field_value in custom-field schemas - #321
fix(opportunities): add fieldValue (preferred) + deprecate field_value in custom-field schemas#321MCPVOT wants to merge 1 commit into
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
| Infrastructure as Code | View in Orca |
🛡️ The following IaC misconfigurations have been detected
| NAME | FILE | ||
|---|---|---|---|
| Template Path With No Corresponding Path Parameter | ...s/opportunities.json | View in code | |
| Template Path With No Corresponding Path Parameter | ...s/opportunities.json | View in code | |
| Template Path With No Corresponding Path Parameter | ...s/opportunities.json | View in code | |
| Template Path With No Corresponding Path Parameter | ...s/opportunities.json | View in code | |
| Template Path With No Corresponding Path Parameter | ...s/opportunities.json | View in code | |
| Template Path With No Corresponding Path Parameter | ...s/opportunities.json | View in code | |
| Template Path With No Corresponding Path Parameter | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Object Without Required Property | ...s/opportunities.json | View in code | |
| Schema Has A Required Property Undefined | ...s/opportunities.json | View in code | |
| Security Requirement Object With Wrong Scopes | ...s/opportunities.json | View in code | |
| Security Requirement Object With Wrong Scopes | ...s/opportunities.json | View in code | |
| Security Requirement Object With Wrong Scopes | ...s/opportunities.json | View in code | |
| ... | ... | ... | ... |
Annotations
Check warning on line 1108 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Template Path With No Corresponding Path Parameter
Details:
OpenAPI path templates containing parameters (e.g., `/users/{userId}`) must
define corresponding path parameters in operation objects with 'in' set to
'path'. Missing parameter definitions break API contracts and cause runtime
errors when consumers attempt invalid requests. Define all templated path
parameters in operation parameter lists.
Recommendation:
Template path parameter should have an operation parameter with the same name and
'in' set to 'path'
Check warning on line 1130 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Template Path With No Corresponding Path Parameter
Details:
OpenAPI path templates containing parameters (e.g., `/users/{userId}`) must
define corresponding path parameters in operation objects with 'in' set to
'path'. Missing parameter definitions break API contracts and cause runtime
errors when consumers attempt invalid requests. Define all templated path
parameters in operation parameter lists.
Recommendation:
Template path parameter should have an operation parameter with the same name and
'in' set to 'path'
Check warning on line 667 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Template Path With No Corresponding Path Parameter
Details:
OpenAPI path templates containing parameters (e.g., `/users/{userId}`) must
define corresponding path parameters in operation objects with 'in' set to
'path'. Missing parameter definitions break API contracts and cause runtime
errors when consumers attempt invalid requests. Define all templated path
parameters in operation parameter lists.
Recommendation:
Template path parameter should have an operation parameter with the same name and
'in' set to 'path'
Check warning on line 586 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Template Path With No Corresponding Path Parameter
Details:
OpenAPI path templates containing parameters (e.g., `/users/{userId}`) must
define corresponding path parameters in operation objects with 'in' set to
'path'. Missing parameter definitions break API contracts and cause runtime
errors when consumers attempt invalid requests. Define all templated path
parameters in operation parameter lists.
Recommendation:
Template path parameter should have an operation parameter with the same name and
'in' set to 'path'
Check warning on line 1017 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Template Path With No Corresponding Path Parameter
Details:
OpenAPI path templates containing parameters (e.g., `/users/{userId}`) must
define corresponding path parameters in operation objects with 'in' set to
'path'. Missing parameter definitions break API contracts and cause runtime
errors when consumers attempt invalid requests. Define all templated path
parameters in operation parameter lists.
Recommendation:
Template path parameter should have an operation parameter with the same name and
'in' set to 'path'
Check warning on line 748 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Template Path With No Corresponding Path Parameter
Details:
OpenAPI path templates containing parameters (e.g., `/users/{userId}`) must
define corresponding path parameters in operation objects with 'in' set to
'path'. Missing parameter definitions break API contracts and cause runtime
errors when consumers attempt invalid requests. Define all templated path
parameters in operation parameter lists.
Recommendation:
Template path parameter should have an operation parameter with the same name and
'in' set to 'path'
Check warning on line 841 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Template Path With No Corresponding Path Parameter
Details:
OpenAPI path templates containing parameters (e.g., `/users/{userId}`) must
define corresponding path parameters in operation objects with 'in' set to
'path'. Missing parameter definitions break API contracts and cause runtime
errors when consumers attempt invalid requests. Define all templated path
parameters in operation parameter lists.
Recommendation:
Template path parameter should have an operation parameter with the same name and
'in' set to 'path'
Check warning on line 731 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 1442 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 822 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 1091 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 567 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 915 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 1274 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 410 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 2199 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 1191 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 998 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 495 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields
Check warning on line 137 in apps/opportunities.json
orca-security-us / Orca Security - Infrastructure as Code
[INFO] Object Without Required Property
Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.
Recommendation:
tags has all required fields