Hi, for a monorepo based architecture that include...
# seed
w
Hi, for a monorepo based architecture that includes FE/BE, is it possible to ignore a full deployment if a change is made to the FE code that has no effect on the BE services?
c
their guide has a section talking about this and you’d basically think of the FE as a package where Lerna looks for changes. https://serverless-stack.com/chapters/using-lerna-and-yarn-workspaces-with-serverless.html
f
@Wernsen is FE a service you added to Seed as well?
w
@Frank This may be a side question but my folder structure currently looks like this
Copy code
- services 
  - users-api (serverless)
  - ml-api (ml code)
- common
I want serverless to deploy the users-api if I make a change to common but not deploy if I make a change to ml-api. The ml-api is deployed through different tooling OR is it recommend/possible to run just a buildspec file with seed if I register it as a service?
f
hmm.. do you have just 1 serverless service?
w
currently have 4 serverless services and 4 different ml services
f
Got it! Yeah the best approach is as @Chuck Carpenter suggested to setup Lerna and Yarn workspaces - https://seed.run/docs/incremental-service-deploys.html#use-lerna-to-check-updated-packages
Then Seed will automatically figure out that the
ml-api
package is not a dependency for
users-api
, hence changes in
ml-api
won’t trigger
users-api
to deploy.