Hello there, I started to switch from Serverless ...
# seed
t
Hello there, I started to switch from Serverless Framework to SST, but I have an issue when adding a new SST service in SEED. 1. My SEED pipeline contains the following stages: a. DEV => (feature branches) b. STAGING => (dev branch) c. PRODUCTION => (master branch) 2. I create a new SST service
HELLO
in a
feature_A
branch. 3. I declare a new service in SEED for
HELLO
, and define the service in my deployment phases. 4. I push my
feature_A
branch, so it's deployed in my DEV stage, and it deploys my
HELLO
service. 5. I merge in my
dev
branch another feature,
feature_B
, which doesn't include the new
HELLO
service. 6. It triggers deployment on stage
STAGING
, but it will fail because
STAGING
tries to deploy the service
HELLO
, which doesn't exist in the
dev
branch. The same with a Serverless Framework service is handled by SEED, the service is skipped, and the deployment phases continue without failing. Can you explain to me know the right way to add a new SST service in SEED? Thanks
f
Hey @Thibault, let me take a look.
We are rolling out an update to handle this case. I will keep you posted once it’s ready.
t
šŸ™Œ
f
Hey @Thibault, we just pushed out an update for this. Give it a try!
the not found SST service should be skipped now
t
@Frank I confirm, works like a charm šŸ˜ As always SEED's support is super quick and efficient šŸŽÆ Thanks a lot
a
@Thibault I liked your ā€œfeature branchā€ approach. How do you deploy each feature branch to
dev
? I don’t find a way to point multiple branches to one stage.
Oh, is this the option? so new stages are created for each branch?
t
@AdriĆ”n Mouly yes it is šŸ‘
a
Thanks sir.