-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Management Policies Support incomplete? #190
Comments
@MisterMX do you have a rough timeline for the next release? |
There is no roadmap for releases. We ususally schedule them once there are changes to be released. |
Would it be possible to cut a release soon for this enhancement? Reza (engineer who submitted the PR) and I work on the same project that needs this feature where controlling how updates are performed is an important control on the platform. |
How do you pass the flag here to enable this feature? |
This should give you what you need: apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
name: provider-argocd
annotations:
argocd.argoproj.io/sync-wave: "-17"
spec:
package: "{{ .Values.image.repository }}/crossplane-contrib/provider-argocd:{{ .Values.argocdProvider.image.tag }}"
runtimeConfigRef:
name: argocd-runtime-config
---
apiVersion: pkg.crossplane.io/v1beta1
kind: DeploymentRuntimeConfig
metadata:
name: argocd-runtime-config
annotations:
argocd.argoproj.io/sync-wave: "-20"
spec:
deploymentTemplate:
spec:
selector: {}
template:
spec:
containers:
- name: package-runtime
args:
- --enable-management-policies
{{ if .Values.argocdProvider.debug }}
- -d
{{ end }}
|
What happened?
I have enabled the
--enable-management-policies
using aDeploymentRuntimeConfig
for the ArgoCD provider.The logs show that is enabled during startup
Proof flag is enabled on the pod
However, Project and Repository resources complain that the managementPolicies I pass in are not recognized
Looking at the trace:
How can we reproduce it?
What environment did it happen in?
Crossplane version: 1.16
Crossplane Provider argocd version: v0.8.0
Cloud provider or hardware configuration: AWS EKS
Kubernetes version (use
kubectl version
): 1.29The text was updated successfully, but these errors were encountered: