Added cli/.run folder to share run-configs through Rider (its similar to sharing a Postman library between a team);
Added --beamable-dev flag to NewMicroservice command (will create the SAMS with the BeamableDev dockerfile)
Moved set-packages.sh script into repo root and added sync-rider-run-settings.sh script to root as well (to share run-configs across team) as a form of discoverability and workflow improvement
Updated template project to contain two Dockerfiles one for beamable developers and another for customers; the BeamableDev one sets us up to build microservice images that reference our own locally built nuget packages
fixed issue with Unreal Microservice Client codegen's Build.cs file
Notes
When you are merging a feature branch into main, please squash merge and make sure the final commit contains any relevent JIRA ticket number. If you are merging from main to staging, or staging to production, please use a regular merge commit.
Does this introduce tech-debt? If so, have you added an entry to the Tech-debt document?
Ticket
https://github.com/beamable/BeamableProduct/issues/3373
Brief Description
Notes
When you are merging a feature branch into
main
, please squash merge and make sure the final commit contains any relevent JIRA ticket number. If you are merging frommain
tostaging
, orstaging
toproduction
, please use a regular merge commit.Does this introduce tech-debt? If so, have you added an entry to the Tech-debt document?