With an update to our compliancy policy, we will begin notifying and deactivating inactive accounts that use our cloud.gov IDP for authentication. Our customers that use their agencies’ credentials to authenticate into our platform will not be affected. Users that do not log into the platform within the past 90 days will be deactivated. We will send you email notifications 10 days and 1 day before deactivation instructing you to log into the platform to reset the 90 day threshold. If you are unable to log into the platform within the allotted time, you will need to email firstname.lastname@example.org to have your account reactivated.
We have put together a new video tutorial to focus on new features of the cf7 CLI. This tutorial will get you familiar with the new “rolling” app deployment strategy available for zero downtime deployments. With these new features available in the cf7 cli, the rolling, zero-downtime deployment option is the most anticipated feature and could improve your workflows the most. The older versions of cli did not provide zero downtime deployments natively which meant needing to use a third party plugin or complicated blue/green deployment pipeline to accommodate your needs.
As part of our reliability and stability enhancements to cloud.gov, the legacy Redis 3.2 and Elasticsearch 5.6 offerings from cloud.gov will be deprecated as of April 5, 2021. In accordance with our deprecation policy, provisioning of new instances will be disabled on December 6, 2020 and on April 5, 2021 we will shut down all active instances. This work is an important step in moving cloud.gov towards a more stable and reliable platform by moving away from a bespoke Kubernetes cluster to AWS-hosted services. Learn more about our deprecation policy here:https://cloud.gov/docs/technology/responsibilities/#deprecation-policy
Learn more about how you can run .NET apps on the cloud.gov platform and get answers to commonly asked questions about .NET development and deployment for cloud.gov
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.