Closed isum closed 1 month ago
It actually pauses and resumes the first of the two deployments. The second one is not accessible. Both names would point to the whichever happens to be first. If that's desired behaviour then is fine IMO.
In node/src/manager/deployment.rs
, there's a similar helper locate_unique
. I don't think this duplication is a big deal, just wanted to point that out.
@lutter The code duplication will eventually be eliminated once more commands are added to Graphman GraphQL API.
There was an issue that prevented
graphman restart
from running if a deployment ID was referenced by multiple subgraph names. This PR fixes that.Closes #5670