64
Expose a Gatsby Cloud management API
planned
Activity
Newest
Oldest
S
Shruti Chaturvedula
planned
Mahesh Warnasooriya
It would be useful to have APIs for everything we can currently do in UI / portal. We will have over 60 gatsby websites and it would be useful to automate the everything from site creation to ongoing maintenance (adding variables, enable/disables builds, add/remove users etc).
Bonus: create a terraform provider for gatsby cloud management! (perhaps this should be a seperate item)
Steven Gresh
Mahesh Warnasooriya: We are currently using netlify as our build platform b/c it has an API and a terraform plugin. We also manage dozens of sites and it'd be impossible to do on gatsby cloud at the moment.
เชษฐ์ โพธิ์ทอง
Mahesh Warnasooriya:
Dmitry Pashkevich
I'd like to be able to set environment variables (including for each preview build individually) via an API
Tomás Peralta
I think this would be awesome for non-technical clients that want to check on their deployments' status. I guess the possibility of re-deploying something would be helpful, in case a deploy breaks and wants to re run it just in case before contacting the development team.
saurabh jain
Tomás Peralta: Also, seeing build Trigger source and trigger status.
Geert Michiels
I really could use this for projects where we need own control over the builds. What I am looking for:
- list of currently queued builds (with details such as incremental/full, source of trigger...)
- possibility to remove a build
- trigger a new build (I know its already partially possible via web hook but still for consistency reasons its nice to have it in same API)
- list of finished builds and their build times (split up in different sections: upload....)
Nicholas Martin
Useful for building dashboards, or triggering a rebuild via a slack command.
Kyle Mathews
gatsby-source-gatsby-cloud — recursion!
Joel Smith
under review
This sounds like a great idea. What are some of the specific admin actions you'd like to manage via the API?
Henri De Roeck
Joel Smith: I am in a scenario where I expect multiple sequential builds, that will take some time to build. I am creating a function to "bundle" these builds (capture the payload before the Gatsby Cloud webhook is called, call the Gatsby webhook with the combined data every 5 minutes).
To be more efficient, I would like to implement this not based on number of minutes, but based on the status of the current build process (if any) and on the fact if there are queued builds already preseent (in which case I would wait longer). That way, I will not only avoid generating a large number of queued builds but I will also be able to trigger a build once there are no longer any builds running and make max usage of the my resources.
This would require me to do a request to Gatsby Cloud to get a status of the queued builds for my site, like using a management API.
Jochen Bertels
Joel Smith My scenario was mostly about being able to update configuration automated for my +200 sites. Enable/Disable cloud or preview builds, change env variables(!), change branch being build, add / remove users, change access for users, ...
Also useful would be an endpoint to fetch the status of builds, history of builds, trigger a new build,...
Shawn Grona
Joel Smith: I have a use case where Gatsby built pages are included in a search service. These pages are created dynamically, I need to know when the build completes so that I can add the particular page to the search service.
Steven Gresh
Joel Smith: Our company wants to use gatsby cloud as the build step in a self-service website builder platform. In this case, our clients are using our custom built UI, meaning we need to be able to create projects and update environment variables completely via the API.
J
Joseph Markus
Joel Smith: restarting failed builds