CrossPlane Compositions Re-architecture #25
Conversation
Signed-off-by: Elamaran Shanmugam <[email protected]>
|
@nimakaviani @nabuskey Please merge CrossPlane Integrations PR and this PR to make CrossPlane compositions rearchitecture work. |
There was a problem hiding this comment.
We should just get rid of this and direct everything under the other repo if we are going this route.
There was a problem hiding this comment.
the idea has been to keep the integration here. but allow for the development of packages to happen separately. reducing the heavy load on templates in one repo. it is good to have this repo as way to list all the add-ons to a stack but then if they really want to have some templates pulled in, they pull them from the dedicated repo.
we separate the Crossplane and TF stuff because it provides easier boundaries on the work and the interest of folks
There was a problem hiding this comment.
I agree that we should get rid of the compositions in this repo
There was a problem hiding this comment.
Shouldn't we just get rid of the crossplane and TF integration folders entirely, then just reference the other repo in readme files? I just don't see why we want to have two different places to keep updating.
There was a problem hiding this comment.
ideally the add-on folder shouldnt need any updating. it only will be for when a new controller (or stack) gets added. we have already been making good amount of changes to the backstage integration repo but the stacks repo hasnt been impacted. same will happen with Crossplane too. cleaning things up and pulling the legacy backstage templates out, we won't have anything else to do with the crossplane folder in this repo.
That said, lets revisit this again maybe during the community call this coming Tuesday to see if a better alternative exists.
Signed-off-by: Elamaran Shanmugam <[email protected]>
|
Thanks Nima. @nabuskey Pls merge this. |
This PR is for CrossPlane Compositions Re-architecture.