Hello! We have our Bitbucket repos connected with AWS Lambda. We notice on one of our repos, when we merge a PR into Dev, it is also updating the Lambdas on Staging. This is not desired. Is there a setting that will prevent this behavior of updating both environments
With Staging what do you mean exactly? Is this another branch called staging or is it an environment in a deploy plan?
If it's a branch: can you see who the author of the merge is? Perhaps it is being done by a build plan? (cascading merge does not exist on Bitbucket Cloud so it can not be a repo setting)
If it's a deploy: can you check the triggers of that plan?
Appreciate your feedback. We actually think the error is on the AWS side after doing more research.
thanks for reaching out!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.