Allow specifying projects for release deploys

[BYK]

Problem Statement

We have a monorepo that houses 4+ projects. They are versioned by the common git SHA so they share the same release id. That said we don't necessarily deploy them all at the same time.

I was trying to create a deploy per each project but seems like the create deploy API endpoint does not support passing individual projects (unlike the create release endpoint).

I'd love to be able to specify which projects the deploy was made for.

Solution Brainstorm

Seems like under the hood, Sentry supports this. Only missing thing is accepting an array of project slugs/ids in the API endpoint and respecting them here:

sentry/src/sentry/api/endpoints/release_deploys.py

Lines 112 to 118 in 8213db2

	for project in projects:
	ReleaseProjectEnvironment.objects.create_or_update(
	release=release,
	environment=env,
	project=project,
	values={"last_deploy_id": deploy.id},
	)

Happy to submit a PR if this sounds good to the team.

[getsentry-release]

Routing to @getsentry/owners-releases-ui for triage. ⏲️

[getsentry-release]

Routing to @getsentry/workflow for triage. ⏲️

[fanley-sentry]

Hi @BYK how does this work for those that don't have this workflow? If they have micro services for example.

[BYK]

@fanley-sentry @Kobby-Bawuah It will work as usual when no projects are specified but will only limit to projects when some/any passed.

If they have micro services for example.

We also have microservices in the same repo which is why we have this issue exactly. I think you meant multi-repo setups?

[BYK]

I think this can easily be relevant for #34327

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀