The capabilities of cloud.gov are vast, and like many initial cloud.gov users, you may be unsure what access level best suits your team. In our experience, we have seen that users who sign up for a cloud.gov sandbox space have the ability to easily scale and adapt their work.
This message is to let you know about upcoming changes to cloud.gov’s CDN and domain services.
On March 31, the cloud.gov team kicked off our Tech Talk series in partnership with Digital.gov University. The series is designed to provide a deeper dialogue on the functionality of cloud.gov while providing guidance on ways to simplify and accelerate development using the platform.
The new beta dashboard is here, making it easier for you to manage orgs and spaces.
In Q3 of FY2019, In the last quarter, we’ve deployed the platform about 150 times. Most of these fixes were patches, security updates, and configuration changes. This month, there was a major release of the cf-deployment: v12.0.0. We’ve integrated this release into our deployment, applied our normal changes to it, tested it, and deployed it.
We want to talk about two crucial aspects of being a cloud provider: consistency and predictability. Consistency is the ability to do something the same way every time, and predictability means that you can count on it happening. When it comes to communicating changes about our platform, we believe we have been neither consistent nor predictable, and we’d like to talk about how we intend to change that.
Cloud.gov’s funding source (the Acquisition Services Fund) requires us to review our expenditures and adjust rates to cover the cost of running the service. Starting on October 1, 2019, new interagency agreements (including renewals) will use the following prices. Agreements already in place will not change, and any modification or amendment to an existing agreement in FY20 will retain the original rate until FY21.
Curious what’s new that you might find helpful as a cloud.gov user? Here are highlights from our recent changes.