-
Notifications
You must be signed in to change notification settings - Fork 50
Open
Labels
bugSomething isn't workingSomething isn't working
Description
What happened?
When creating a Token, the secret details are not written to the secret specified in writeConnectionSecretToRef. The secret details do populate after an update.
How can we reproduce it?
echo "apiVersion: projects.argocd.crossplane.io/v1alpha1
kind: Project
metadata:
name: example-project
spec:
forProvider:
projectLabels:
argocd.crossplane.io/global-project: 'true'
sourceNamespaces:
- default
roles:
- name: example-role
groups:
- example-group
policies:
- p, proj:example-project:example-role, applications, *, example-project/*,
allow
providerConfigRef:
name: argocd-provider
---
apiVersion: projects.argocd.crossplane.io/v1alpha1
kind: Token
metadata:
name: example-token
spec:
forProvider:
id: example-token
project: example-project
role: example-role
renewAfter: 1s
providerConfigRef:
name: argocd-provider
writeConnectionSecretToRef:
name: example-token
namespace: default" | kubectl apply -f -
Review the secret, it has no data...
kubectl get secrets example-token -o yaml
NAME TYPE DATA AGE
example-token connection.crossplane.io/v1alpha1 0 50m
When the token is updated (tested by setting renewAfter to 10s), the token is populated correctly
What environment did it happen in?
Crossplane version: 1.19.1
Crossplane Provider argocd version: 0.10.1
dunkin0486
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working