colearendt
commented
2 years ago Hello @roberts2727 ! Thanks for reaching out here! That is a fantastic question!
Unfortunately the answer depends a bit on your target / setup. My two general recommendations would be as follows:
- If you want to traverse the "functional dependency tree" then deploy in order: Package Manager -> Connect -> Workbench
- The idea here is that Connect is often configured with RSPM's URL and Workbench is configured with RSPM and Connect's URL
- RSPM is the "source" of packages, Connect is the "publishing environment," and then RSW uses both to install / deploy things
- RSPM is also sometimes "easier" to set up, particularly when using cloud storage (i.e. S3), and it has no auth requirements. Acceptance testing can be done in the UI or from a desktop environment, for instance.
- If you are synchronous with users (i.e. they are testing / using the environment as you build / deploy, offering feedback, etc.), then we see people use the deployment order: Workbench -> Package Manager -> Connect pattern too
- The idea here is to get the "Dev environment" up first for users to "play" / try things
- Then it is easy to acceptance test RSPM as it comes up
- Similarly for Connect. It can be configured to point at RSPM and then users can deploy to it!
I hope that helps! I will keep this issue open so that we can add some documentation that makes this story clearer!
Is there an order of operations that should be followed when deploying these helm charts? We are a new customer that just purchased Team for 5 users and want to deploy into an AKS Environment that has already been setup and is using the AGIC Add On. Should we start with workbench deployment, then add in connect and package manager?