Add PagesDeployment to deletePagesDeployment Mutation
What does this MR do and why?
This commit adds the deleted PagesDeployment as a field to the deletePagesDeployment mutation
This will allow the frontend to update the deployments state in the apollo cache.
MR acceptance checklist
How to set up and validate locally
- Set up your GDK to support Runners and Pages
- Create a Pages project, by creating a new project with the "pages/Plain HTML" template within a group
- ensure the pipeline runs so that a pages deployment is created.
- obtain the deployment's global ID with the following Graphql Query:
query GetNamespacePagesDeployments {
namespace(fullPath: "<PATH OF THE GROUP>") {
pagesDeployments {
nodes {
id
active # this should be true
}
}
}
}
- Now run the below mutation:
mutation DeletePagesDeployment {
deletePagesDeployment(input: { id: "<PAGES_DEPLOYMENT_GLOBAL_ID>" }) {
pagesDeployment {
id
active
deletedAt
}
errors
}
}
- You should now see the "active" property of the deployment as "false" and a value for the "deletedAt" property