Replies: 1 comment
-
This is something we are also struggling with, would be really good if we can find some solution with this else automating this with cross plane will be really hard in many use cases. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description:
I've been working on combining resources for the ArgoCD provider using Crossplane compositions, specifically for provisioning Projects, Repositories, and Application objects.
Problem Statement:
When I create a Crossplane claim for a Repository, the ArgoCD provider generates a managed resource with a name that combines the claim name (e.g., test-repo) and a random string. This part works as expected. However, the challenge arises when I want to reference this Repository claim in a Project claim. The ArgoCD provider will search for the Repository within the managed resources rather than the claims which is the expected behavior.
Claims
Here are the relevant configurations I'm using for the Repository and Project:
Repository
Project
I'm seeking guidance and best practices on how to handle this situation. Specifically, I'd like to understand how to ensure that the Project claim can correctly reference the Repository claim, considering the unique names used in claims.
Beta Was this translation helpful? Give feedback.
All reactions