ensure core package customizations are processed

[nabuskey]

fixes: #298

One thing to note when overwriting argocd CMs is that you need to have the labels on the CM. Otherwise, ArgoCD will complain about not finding argocd-cm CM.

apiVersion: v1
kind: ConfigMap
metadata:
  name: argocd-cm
  labels: # these labels need to be present.
    app.kubernetes.io/name: argocd-cm 
    app.kubernetes.io/part-of: argocd
data:
  application.resourceTrackingMethod: annotation
  resource.exclusions: |
    - kinds:
        - ProviderConfigUsage
      apiGroups:
        - "*"
  timeout.reconciliation: 10s

@csantanapr ^^

[blakeromano]

I also don't really see much documentation around how this feature is supposed to be invoked/used...

Is this a CLI argument to idpbuilder create?

[blakeromano]

Can we make this an enum?

[blakeromano]

is the plan to not support helm or kustomize?

[csantanapr]

Good catch on the labels @nabuskey

[csantanapr]

/lgtm

[nabuskey]

I also don't really see much documentation around how this feature is supposed to be invoked/used...

Is this a CLI argument to idpbuilder create?

We do need to do a better job of documenting these.
See: #180