Inconsistency between creating a Project and a Team programmatically when the Project/Team already exists

Description

The following code is executed to create a Project.

If the project `project_name` already exist AND if the synapse user who run the code is the owner (or has edit access?), then no exception is raised and a handle to the Project is return.

Note: This behavior contradicts the documentation that simply states:

> Projects in Synapse must be uniquely named. Trying to create a project with a name that’s already taken, say ‘My project’, will result in an error

See https://python-docs.synapse.org/build/html/Entity.html?highlight=project

Let's now consider the following code to create a Team

In the scenario where the team `team_name` already exists AND the user running the code is the owner of the Team, then an exception is raised. If the user expects the creation of Project and Team to behave similarly, then a handle to the team should have been returned in the above scenario (or have the creation of Project fail).

Environment

None

Assignee

Unassigned

Reporter

Thomas Schaffter

Labels

Validator

Kenneth Daily

Development Area

None

Release Version History

None

Affects versions

Priority

Minor
Configure