> ## Documentation Index > Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt > Use this file to discover all available pages before exploring further. # List GitOps conflicts > Lists the cluster's open GitOps merge conflicts (`ankra cluster gitops conflicts list`): resources changed both in the GitOps repository and on the platform since they last agreed. GitOps sync stays paused on them until each is resolved. Each entry names the resource, how Git (`git_change_type`) and the platform (`db_change_type`) changed it, and any resolution already recorded that the next sync will apply. Any member of the cluster's organisation can read it. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json get /api/v1/org/clusters/{cluster_id}/gitops/conflicts openapi: 3.1.0 info: title: FastAPI version: 0.1.0 servers: - url: https://platform.ankra.app security: [] tags: - name: Organisation IAM description: >- Custom organisation roles and scoped role assignments for member and service-account identities. - name: Clusters description: Create, inspect and manage clusters, and the stacks deployed on them. - name: Managed Clusters description: Provider-managed control planes, driven through one common surface. - name: Imported Clusters description: Clusters that already existed and were connected to Ankra. - name: Cluster Access description: Kubeconfigs, service-account tokens and per-cluster access grants. - name: Kubernetes description: Read and act on the Kubernetes objects inside a cluster. - name: AWS Clusters description: >- Provision and manage self-managed k3s / kubeadm clusters on AWS EC2 in your own VPC. - name: Ankra Cloud Clusters description: >- Provision and manage self-managed kubeadm / k3s clusters on Ankra Cloud servers: a private network, a NAT router and a bastion per cluster. - name: DigitalOcean Clusters description: Provision and manage DigitalOcean Kubernetes clusters. - name: Hetzner Clusters description: Provision and manage Hetzner Kubernetes clusters. - name: OVH Clusters description: Provision and manage OVH Kubernetes clusters. - name: Scaleway Clusters description: Provision and manage Scaleway Kapsule clusters. - name: UpCloud Clusters description: Provision and manage UpCloud Kubernetes clusters. - name: Applications description: Deploy, configure and observe applications across the fleet. - name: Pipelines description: >- Pipeline definitions, the approval of the authority they declare, and the caches pipelines keep between runs. - name: Deploy Targets description: >- Environments, the hosts registered to receive deployments, and the releases deployed to them. - name: Backups description: >- Backup vaults, restore points, protection posture and captures for stacks and application deployments; a completed capture is not a verified restore. - name: Stack Profiles description: Reusable stack definitions, their versions and sharing. - name: Services description: >- Versioned service packages and explicit sharing. Runtime admission is separate from publication. - name: Charts description: Browse the chart catalogue behind stacks and addons. - name: Helm description: Helm registries, credentials and the charts they expose. - name: Executions description: Long-running platform executions and their jobs. - name: Operations description: Cancel in-flight cluster operations and their jobs. - name: Chat description: Conversational sessions, plans and confirmable actions. - name: AI Management description: >- Customer agent lifecycle, authenticated identity and organisation automation controls. - name: AI Agent Runs description: Autonomous agent runs and their outcomes. - name: AI Tickets description: The AI ticket board, its sync connections and settings. - name: AI Playbooks description: Reusable playbooks the AI lanes execute. - name: AI Conditions description: Conditions that gate AI autonomy. - name: AI Remediation description: >- The organisation's auto-remediation policy: what the AI lanes may fix by themselves, and who approves the rest. - name: AI Engineering Handoffs description: Work the AI lanes escalate to a human engineer. - name: AI Environment description: The environment and base stacks AI demos deploy into. - name: Security description: Findings, advisories, SBOMs, compliance and posture. - name: Cost description: Cluster and fleet cost, rate cards and cost settings. - name: Decisions description: >- The decision ledger behind the Security and Cost queues: proposals a surface computed, the approve and set-aside decisions people took on them, and the receipts of running them. - name: Billing description: Subscription and spend caps. - name: Organisation description: Members, invitations, audit logs and organisation settings. - name: Account Tokens description: Personal access tokens for the API and CLI. - name: Credentials description: The shared credential store. - name: AWS Credentials description: >- AWS credentials: access keys or CloudFormation-onboarded STS roles for cost, EKS and self-managed provisioning. - name: Ankra Cloud Credentials description: >- Ankra Cloud API tokens, shared by the self-managed and managed Ankra Cloud lanes. - name: Azure Credentials description: Azure credentials and SSH keys. - name: DigitalOcean Credentials description: DigitalOcean credentials and SSH keys. - name: Hetzner Credentials description: Hetzner credentials and SSH keys. - name: OVH Credentials description: OVH credentials and SSH keys. - name: Scaleway Credentials description: Scaleway credentials. - name: UpCloud Credentials description: UpCloud credentials and SSH keys. - name: Data Source Credentials description: Credentials for metrics and log sources. - name: DNS Credentials description: Credentials for DNS providers. - name: Object Storage Buckets description: >- Buckets Ankra creates and manages on an organisation's own provider credentials. - name: DNS description: DNS zones and records, including custom organisation zones. - name: Cloudflare description: Cloudflare domains and the credentials behind them. - name: Avura description: >- The linked Avura organization, the domains it shares with Ankra Platform, and their DNS records. - name: Variables description: Organisation- and cluster-scoped variables. - name: SOPS description: Encrypt and decrypt values with the organisation SOPS config. - name: Alerts description: Alert integrations and ingest credentials. - name: Notifications description: Notification routes and their delivery targets. - name: Support description: Support tickets. - name: AI Settings description: Organisation AI provider, model catalog and per-function model settings paths: /api/v1/org/clusters/{cluster_id}/gitops/conflicts: get: tags: - Clusters summary: List GitOps conflicts description: >- Lists the cluster's open GitOps merge conflicts (`ankra cluster gitops conflicts list`): resources changed both in the GitOps repository and on the platform since they last agreed. GitOps sync stays paused on them until each is resolved. Each entry names the resource, how Git (`git_change_type`) and the platform (`db_change_type`) changed it, and any resolution already recorded that the next sync will apply. Any member of the cluster's organisation can read it. operationId: >- list_gitops_conflicts_api_v1_org_clusters__cluster_id__gitops_conflicts_get parameters: - description: PAT organisation override. in: header name: x-ankra-organisation-id required: false schema: type: string - name: cluster_id in: path required: true schema: type: string format: uuid responses: '200': content: application/json: schema: $ref: '#/components/schemas/GitOpsConflictListResponse' description: The cluster's open conflicts, ordered by resource key. '400': content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' description: Missing or malformed Authorization header '401': content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' description: Unknown, expired, or revoked API token '403': content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' description: >- The token may not use this surface: an MCP-scoped token, or an organisation override naming an organisation the token's user is not a member of '404': content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' description: Cluster not found in the token's organisation '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Request validation error security: - BearerAuth: [] components: schemas: GitOpsConflictListResponse: properties: conflicts: items: $ref: '#/components/schemas/GitOpsConflict' title: Conflicts type: array total: title: Total type: integer required: - conflicts - total title: GitOpsConflictListResponse type: object ContractDetailError: example: detail: Cluster not found properties: detail: oneOf: - type: string - additionalProperties: true properties: {} type: object required: - detail type: object HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object GitOpsConflict: description: One open GitOps merge conflict. properties: resource_key: description: >- Identifies the conflicting resource, for example `stack:web/addon:nginx`. Pass it to the resolve-resource route. title: Resource Key type: string stack_name: anyOf: - type: string - type: 'null' title: Stack Name resource_kind: description: >- What the key names: `stack`, or the kind of a stack member such as `addon` or `manifest`. title: Resource Kind type: string resource_name: anyOf: - type: string - type: 'null' title: Resource Name git_change_type: description: >- How the GitOps repository changed the resource since the last agreed state, for example `added`, `modified` or `removed`. title: Git Change Type type: string db_change_type: description: >- How the platform's record of the resource changed since the last agreed state, for example `added`, `modified` or `removed`. title: Db Change Type type: string last_applied_commit_sha: anyOf: - type: string - type: 'null' title: Last Applied Commit Sha detected_at: anyOf: - type: string format: date-time - type: 'null' title: Detected At resolution_choice: anyOf: - enum: - git - cluster type: string - type: 'null' title: Resolution Choice description: >- The recorded resolution waiting for the next sync to apply it; null while the conflict is undecided. resolved_at: anyOf: - type: string format: date-time - type: 'null' title: Resolved At required: - resource_key - stack_name - resource_kind - resource_name - git_change_type - db_change_type - last_applied_commit_sha - detected_at - resolution_choice - resolved_at title: GitOpsConflict type: object ValidationError: properties: loc: items: anyOf: - type: string - type: integer title: Location type: array msg: title: Message type: string type: title: Error Type type: string required: - loc - msg - type title: ValidationError type: object securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.