This document provides an overview over the changes we are making over time. Feel free to reach out to us in case of any specific questions.
- New: Added support for Persistent Volumes.
Mount paths are specied on the workload level.
We will shift the product update to April 9th due to the short break over Easter.
-
New: Forms for adding resource definitions now present fields in a more intuitive order and include help text.
-
Improvement: Draft can now be discarded even if it is the only draft. (A new blank draft is created in its place.)
-
Fixed: Behaviour of clones in the UI is corrected. Clone includes comment from deployment it was created from and is properly represented in the draft. Code version can be updated in the draft applied to clone.
-
Fixed: Submitting variable value now possible when suggestions drop-down is shown.
-
Fixed: Live container statuses sometimes not shown after deployment.
-
New: Pod status is now communicated on the Workload tile in the Active Deployment mode.
-
Fixed: It is now possible to replace a deleted resource definition with a new one of the same type with overlapping matching criteria while the original one is still in pending deletion state.
-
New: Errors at the Environment level are now surfaced in UI.
-
New: Aiven added as an Account Type & documentation added for connecting Aiven managed databases.
-
Improved: Environments and Deployments pane in Workload Details screen expanded and Environment Tabs restructured.
-
Fixed: Clicking outside the Dynamic/Static Resource Definition dialog does not cause all data to be automatically lost.
-
Fixed: Form for specifying static DNS did not handle TLS certificates correctly.
-
Fixed: Many UI inconsistencies.
-
New: Workloads can now depend on multiple resources of the same type.
-
New: Added support for Aiven (Database-as-a-Service provider).
-
Changed: We changed the default deployment behaviour so that workloads no longer wait for a successful readiness probe before terminating the old pods. This means that the state of the namespace will match the requested deployment, but will mean that pods might be in a failed state. These will be reported in the UI. It will also mean deployments complete much faster. We are working on Blue/Green Deployments to provide a reliable way of ensuring environment wide consistency.
-
Improved: Both, our GitHub Action as well as our CircleCI Orb, now support the specification of additional docker arguments (e.g.,
build-args
). -
Improved: Updated documentation of environment variables & secrets and container configuration.
-
Fixed: Failing application deletion in the case of deployment errors.
-
Fixed: Last environment in an application can no longer be deleted.
Here is our first product update 2021. We started with some important new features into the new year.
-
New: We created an Environment Settings Screen that bundles all environment-specific settings. We moved the Automation Rules and environment-specific Shared values and secrets overrides into this new screen. We now also allow users to specify a namespace in Kubernetes for each environment. This has been supprted by the API but not by the UI.
-
New: We are now allowing users to delete environments directly from the environment dropdown menu on the App Details Screen.
-
New: Out-of-the-box support for Amazon S3 buckets as Dynamic Resources.
-
Improved: Support multi-line values in Shared values and secrets.
-
Improved: Listing of dynamic resources.
-
Fixed: Adding overrides for shared variables cause console error Cannot read property 'id' of undefined.
-
Fixed: Missing UI elements after creating a new environment.
We enjoyed some time off between the years and we hope you did too. Stay tuned for the first product update 2021 which we will publish on January 22nd.
-
New: Add configuration as a file that will be accessible from your container (UI&API).
-
New: Specify Service account that a pod should adopt via UI.
-
New: Create Webhooks Deployment (started/finished) and Environment (created/deleted) events. (UI&API).
-
Improved: Show deployers for all deployments.
-
Improved: Show who created a resource definition.
-
Improved: User experience for re-deploying a historical deployment set.
-
Fixed: It’s not possible to remove command overwrites and args.
-
Fixed: The overview of deploy changes does not show removed env variables.
-
Fixed: Container images dropdown for adding a workload is partially hidden.
-
Fixed: Adding substitute variables for s3bucket.
-
Fixed: Small UI issues on Firefox.
-
Fixed: Blinking smiley behavior :-)
-
Improved: Environments are ordered by creation date instead of alphabet.
-
Improved: Users can choose to delete an environment type and see associated environments.
-
Improved: A lot of great styling updates!
-
Fixed: After adding a managed workload (Redis) the workload dropdown selection is not cleared.
-
Fixed: Selecting placeholder from prompt popup causes currently entered text to be ovewritten.
-
Fixed: After creating a draft from a diff the module detail page is not updated.
-
Fixed: Envtype list is cut off on static resources page.
-
Fixed: After deploying the user can directly see the currently running version instead of the draft.
-
Fixed: Variables are not displayed in the diff if it is removed.
-
Fixed: S3 bucket should only be available for adding to module when a S3 resource definition exists.
-
Fixed: user reported issues with user pagination and user invite via Github.
-
Improved: Based on user feedback, changed Modules to Workloads across application.
-
New: A "My Apps" screen with all applications that a user has an access to as well as their respective environments. The user can choose to open the required application or an environment directly from the My Apps screen.
-
New: Redirect to "My Apps" after deleting an application.
-
New: Introduced an error screen for javascript errors and 404s with a redirect to "My Apps".
-
Fixed: Automated deployments do not show up in UI until they are finished.
-
Improved: Scroll bars across application.
-
New: Deleting Resource Definitions via the UI. If the resource definition has any active resources associated with it, the user is informed about those resources and their suggested replacements. If the user proceeds with the deletion, the resource definition will be marked with pending deletion until all active resources are redeployed.
-
Improved: Input component for shared value overrides.
-
Improved: Snippet for Bitbucket integration.
-
Fixed: Error handling in a case of a blank screen.
-
Fixed: Allowing users to select “None” for static resources that do not need a driver.
-
Fixed: Real-time updates for automated deployments.
-
New: UI and API for adding S3 Bucket resource definition and defining dependency within your modules.
-
New: Welcome emails to newly registered users.
-
Improved: Container runtime status added to application view - users can see at a glance if any of their modules are failing.
-
Improved: Expandable deployment history view. Users can filter based on deployment comment and find their historical deployments easier.
-
Improved: CI integration guide - now presented as a wizzard.
-
New: Export manifests for your chosen deployment set. Manifests can be downloaded as .yaml files and stored in a repository.
-
New: UI support for connecting your own GKE or EKS cluster via Static Resources.
-
Improved: Possibility to add and confirm contact email through profile settings if it is not retrieved during registration.
- New: UI for Runtime status
- View the runtime status for deployed applications and easily debug errors when they occur
- Users are informed if any of the replicas are failing and the affected deployment and modules are marked with a warning
- To simplify debugging, container errors are reported for each replica separately and presented to the user together with the container log
- New: API for deleting resources
- Improved: Live container logs
- Users do not have to refresh to see the latest logs
- Fixed UI issues and logs formatting
- Fixed: Wrong DNS being shown for modules (user reported bug)
- Improved: Container logs
- New: Humanitec CircleCI Orb for simple integration between CircleCI and Humanitec
UI improvements:
Documentation update:
- Release of the API documentation (currently in beta) available here incl. a first tutorial how to use the Humanitec API
General new features:
General new features:
- Allow users to connect dynamic resources of type Postgres with Google Cloud Platform resource account
UI improvements:
New API endpoints:
- API endpoint for deployment automation - allowing users to create, update and delete rules for automated deployments; Humanitec deploy new images automatically based on the defined rules
General new features:
Onboarding support:
General new features:
- Option to create a diff between two deployment sets within one environment
- Allow for patching of environments: apply a diff to a deployment set in any environment
Onboarding support:
- Added sample images that allow for a quicker onboarding (e.g., option to deploy first application without connecting own CI pipelines)
General new features:
- Option to clone deployments to another environment
- Added Elasticsearch and MariaDB as managed images
- Allow to switch between drafts and deployments directly from the module configuration view
New features only available via the API:
- Deploy to your own GCP account (API documentation will be pusblished soon on our docs site)