Open ashishkurian opened 6 hours ago
Hi @ashishkurian 👋
I believe the name is not matching.
The matcher is looking for sc-role-servicerole-insproroashtest
.
- matchers:
- resources:
- name: "sc-role-servicerole-insproroashtest"
That is the name of the resource being created.
apiVersion: iam.aws.crossplane.io/v1beta1
kind: Role
metadata:
name: sc-role-servicerole-insproroashtest
But we match on the "name" key in the desired resource map. This name is derived from the gotemplating.fn.crossplane.io/composition-resource-name
annotation, which is set to InsProRoashtest
.
apiVersion: iam.aws.crossplane.io/v1beta1
kind: Role
metadata:
annotations:
gotemplating.fn.crossplane.io/composition-resource-name: InsProRoashtest
To resolve the issue, either change the matcher to look for InsProRoashtest
, or change the resource name annotation to equal sc-role-servicerole-insproroashtest
.
What happened?
Status transformer failing to propagate conditional message to the Composite resource and Claim even though the
StatusTransformationSuccess
isTrue
on the composite resource.Expectation
I want to propagate the
conditions.InstanceProfileRoleReady
type to be instatus: "False"
withmessage "Encountered an error creating the instance profile role: <the error that I am capturing using regex>"
Current composite resource status conditions
What am I missing or doing incorrect here?
How can we reproduce it?
I am sharing my XRD, Composition and claim below. I assume I can set any type for the
setConditions.condition.type
as I havex-kubernetes-preserve-unknown-fields: true
set under the conditions for the XRD.In my iam role managed resource, I am deliberately creating an error so that I can propagate that error message to the composite and claim.
I have the following error on the managed aws iam role.
Manifest I am using.
What environment did it happen in?
Status transformer function version: v0.4.0 Cloud provider: AWS Kubernetes version: v1.29.1 Kubernetes distribution: EKS Crossplane version: v1.17.3