Adding Support For Optinally Including Inherited and Invited Members …

[mk-armah]

…of Gitlab Groups

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.

Updated docs pages

Please also include the path for the updated docs

• includeInheritedMembers (/build-your-software-catalog/sync-data-to-catalog/git/gitlab-v2/examples?parameter=includeInheritedMembers)
• ...

[aws-amplify-eu-west-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-2838.d2ngvl90zqbob8.amplifyapp.com

[qodo-merge-pro]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Non-code change: The PR only adds documentation examples and does not introduce executable code where audit logging of critical actions could be evaluated. Referred Code <TabItem label="Include Inherited and Invited Members" value="includeInheritedMembers"> You can also specify the `includeInheritedMembers` selector to control the inclusion of inherited and invited members in the member data. By default, this parameter is set to `false`, and the integration will sync only direct members without inherited members and/or invited members. ```yaml - kind: group-with-members selector: query: 'true' # highlight-next-line includeInheritedMembers: true - kind: members selector: query: 'true' # highlight-next-line includeInheritedMembers: true ... (clipped 1 lines) </details> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td><details> <summary><strong>Generic: Meaningful Naming and Self-Documenting Code</strong></summary><br> **Objective:** Ensure all identifiers clearly express their purpose and intent, making code <br>self-documenting<br> **Status:** <br><a href='https://github.com/port-labs/port-docs/pull/2838/files#diff-ead03f449674a9aed1f883e312acad2d8ec95f552117c72257a44b52c626170fR329-R343'><strong>No identifiers added</strong></a>: The PR adds documentation and YAML snippets but no application identifiers or code <br>constructs to assess naming conventions.<br> <details open><summary>Referred Code</summary> ```markdown ```yaml - kind: group-with-members selector: query: 'true' # highlight-next-line includeInheritedMembers: true - kind: members selector: query: 'true' # highlight-next-line includeInheritedMembers: true </details> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td><details> <summary><strong>Generic: Robust Error Handling and Edge Case Management</strong></summary><br> **Objective:** Ensure comprehensive error handling that provides meaningful context and graceful <br>degradation<br> **Status:** <br><a href='https://github.com/port-labs/port-docs/pull/2838/files#diff-ead03f449674a9aed1f883e312acad2d8ec95f552117c72257a44b52c626170fR324-R345'><strong>No error paths</strong></a>: The changes are documentation-only and do not include executable code where error handling <br>or edge cases can be assessed.<br> <details open><summary>Referred Code</summary> ```markdown <TabItem label="Include Inherited and Invited Members" value="includeInheritedMembers"> You can also specify the `includeInheritedMembers` selector to control the inclusion of inherited and invited members in the member data. By default, this parameter is set to `false`, and the integration will sync only direct members without inherited members and/or invited members. ```yaml - kind: group-with-members selector: query: 'true' # highlight-next-line includeInheritedMembers: true - kind: members selector: query: 'true' # highlight-next-line includeInheritedMembers: true ... (clipped 1 lines) </details> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td><details> <summary><strong>Generic: Security-First Input Validation and Data Handling</strong></summary><br> **Objective:** Ensure all data inputs are validated, sanitized, and handled securely to prevent <br>vulnerabilities<br> **Status:** <br><a href='https://github.com/port-labs/port-docs/pull/2838/files#diff-ead03f449674a9aed1f883e312acad2d8ec95f552117c72257a44b52c626170fR329-R343'><strong>Docs only change</strong></a>: The PR introduces documentation and config examples without underlying code where input <br>validation or data handling can be verified.<br> <details open><summary>Referred Code</summary> ```markdown ```yaml - kind: group-with-members selector: query: 'true' # highlight-next-line includeInheritedMembers: true - kind: members selector: query: 'true' # highlight-next-line includeInheritedMembers: true </details> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td align="center" colspan="2"> <!-- placeholder --> <!-- /compliance --update_compliance=true --> </td></tr></tbody></table> <details><summary>Compliance status legend</summary> 🟢 - Fully Compliant<br> 🟡 - Partial Compliant<br> 🔴 - Not Compliant<br> ⚪ - Requires Further Human Verification<br> 🏷️ - Compliance label<br> </details>