Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EES-5639 - Adding the ability to be able to edit the Label for any Release (BE) #5591

Open
wants to merge 29 commits into
base: dev
Choose a base branch
from

Conversation

jack-hive
Copy link
Collaborator

No description provided.

…oid confusion with the upcoming new endpoint
…anging the PUT endpoint for `ReleaseVersions`

The `PUT` route for updating a `ReleaseVersion` has been changed to better reflect the resource it is changing:
It was: `PUT /releases/{releaseVersionId}`
We've changed it to: `PATCH /releaseVersions/{releaseVersionId}`

It only represents a partial update; hence the switch to using `PATCH` rather than `PUT`.

This has been done in preparation for a new Update endpoint for the `Release` itself in a future commit. If we did not change the route for this endpoint now, we'd have conflicting routes.
…stValidators`, and moving the `ReleaseCreateRequestValidator` into a new `ReleaseRequestValidators`
…ePermissionTests` into `ReleaseServicePermissionTests`
…e fact that they're actually checking roles based on the `ReleaseVersion`, not a `Release`
… `UpdateSpecificReleaseVersionAuthorizationHandlerTests`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant