Open lorsal opened 1 year ago
This is still happening with current version: Universal Crossplane Version: v1.15.1 Provider Version: 1.0.0 Kubernetes version (use kubectl version): 1.28.5
Anything i can help to get this issue forward?
observe failed: failed to observe the resource: [{0 parsing "<no value>/federatedIdentityCredentials/test-j7gnh": parsing the FederatedIdentityCredential ID: the number of segments didn't match
Expected a FederatedIdentityCredential ID that matched (containing 10 segments):
> /subscriptions/12345678-1234-9876-4563-123456789012/resourceGroups/example-resource-group/providers/Microsoft.ManagedIdentity/userAssignedIdentities/userAssignedIdentityValue/federatedIdentityCredentials/federatedIdentityCredentialValue
However this value was provided (which was parsed into 0 segments):
> <no value>/federatedIdentityCredentials/test-j7gnh
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale
. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
This issue is being closed since there has been no activity for 14 days since marking it as stale
. If you still need help, feel free to comment or reopen the issue!
Please re-open. This is still relevant.
What happened?
Creation of a
FederatedIdentityCredential
resource as part of a composition fails initially due to an error related to patching thespec.forProvider.parentId
field (or processing the patched value, at least). However, after manually deleting the non-readyFederatedIdentityCredential
object on the crossplane instance, the object is recreated and then successfully processes the patchedparentId
value.Error:
observe failed: cannot run refresh: refresh failed: parsing "parentId/federatedIdentityCredentials/test1-fic": expected 10 segments within the Resource ID but got 3 for "parentId/federatedIdentityCredentials/test1-fic": parsing "parentId/federatedIdentityCredentials/test1-fic": expected 10 segments within the Resource ID but got 3 for "parentId/federatedIdentityCredentials/test1-fic"
How can we reproduce it?
azure-provider-config-team1
kubectl describe federatedidentitycredentials.managedidentity.azure.upbound.io test1-fic
to see error message; note that the value is apparently already successfully patched to the parentId fieldkubectl delete federatedidentitycredentials.managedidentity.azure.upbound.io test1-fic
watch kubectl get federatedidentitycredentials.managedidentity.azure.upbound.io test1-fic
; object will be recreated and reach ready: true statusWhat environment did it happen in?
kubectl version
): 1.25.5FedIdTest.yaml.txt XFedIdTest.yaml.txt claim-fedidtest.yaml.txt