github.com/argoproj/argo-cd@v1.8.7/docs/operator-manual/upgrading/1.6-1.7.md (about)

     1  # v1.6 to 1.7
     2  
     3  ## AppProject tokens moved to status field
     4  
     5  In order to address [argoproj/argo-cd#2718](https://github.com/argoproj/argo-cd/issues/2718) the JWT tokens stored in
     6  AppProject CRD have been moved from `spec` to `status` field. The migration is performed automatically during upgrade
     7  and might cause few seconds delay. No additional side effects besides the delay are expected. It is acceptable to
     8  rollback to previous version - no data loss is expected.
     9  
    10  
    11  ## Resources like ConfigMap might become out-of-sync due to YAML library upgrade
    12  
    13  As part of v1.7 release, the Kubernetes client library have been upgrade to v1.18.8 as well as we've started using
    14  https://github.com/kubernetes-sigs/yaml for YAML handling to be consistent with `kubectl` behavior.
    15  This introduced a change of multiline string handling in resource manifests. As a result, YAML manifests with multiline
    16  strings might become out-of-sync after upgrading and you might have to trigger the synchronization once to resolve it.
    17  
    18  Affected resource example:
    19  
    20  ```yaml
    21  ---
    22  apiVersion: v1
    23  kind: ConfigMap
    24  metadata:
    25    name: my-config-map
    26  data:
    27    value: |+ # block chomping indicator is dropped by Argo CD v1.7 ( same as kubectl apply)
    28    hello
    29  ```
    30  
    31  From here on you can follow the [regular upgrade process](./overview.md).