v0.12 brings enhanced Resource Configuration version history, and lots of enhancements and bug fixes.

✨What's New

• Live and queued marker for Resource Configuration version history
  Users can now view the released status for a Resource Configuration in the version history section. Every time a new configuration is saved, it takes till next deployment to come in effect. With new markers for Live and Queued changes, users can identify the current live configuration.

• Notification channels can now be deleted
  Notification channels that are no longer required can now be deleted from the UI.

📈Enhancements

• Resources of type windows-application will now have access to Live Release, Diff and Grafana Views in Resource Center
• Replaced all charts in Application Live Release with native charts
• Added full screen view for tools
• All Links on Resource Information page are now clickable

🐞 Bug Fixes

• Fixed a bug where logs in UI were not coming up in some cases with only few log lines.
• Fixed a bug where incorrect help text was being displayed while creating GCP Environment.
• Fixed a bug where default values for spot instances was missing while creating AWS Environment.
• Fixed a bug where IaC version were not sorted in the Environment Overview page.
• Fixed a bug where back button from Release Scheduler was taking the user back to Releases page, even if user was coming from Environment Overview page.

v0.11 brings a new Release Modal, Zenduty & PagerDuty support for notifications, Common File Share between all deployed Instances and lots of enhancements and bug fixes.

✨What's New

• New Release Modal with Full and Selective Release options
  Users can now choose to perform a Full Release with options to refresh, force release and allow destructive action during the deployment, or a Selective Release by choosing specific resources from the Release Modal in Releases screen.

• Zenduty & PagerDuty support for Notifications
  Two new Channel Types have been added for creating Notification Subscriptions, namely, Zenduty and PagerDuty. Users can create these Channel Types under the Notifications tab in Organisation Settings screen.

• Availability Rules to launch and destroy ephemeral Environments
  Users can set Availability Rules to launch and destroy ephemeral Environments on schedule. This can be done from the Availability Rules widget under Environment Overview screen.

• Common File Share between all deployed Instances
  Users can now define an NFS (Network File System) in their Blueprint definition to create a file share that can be accessed by all deployed pods. To enable this, add a similar code snippet into your application JSON definition:
  JSON

  "nfs": {
    "name": "myshare",
    "path": "/mnt/myshare"
  }
  

📈Enhancements

• Enhanced Deployment Status Update Notification Type
  Users can now choose the Release Status under Advanced Filters when creating a Notification Subscription of type Deployment Status Update.

• Configurable maximum unavailable pods for deployment
  Users can now configure the max unavailable pods when deploying using the Rolling Update release strategy.
  To enable this, add a similar code snippet into your JSON definition:
  JSON

  "release": {
      "strategy": "RollingUpdate",
      "maxAvailable": 2,
      "maxUnavailable": 0
      }
  }
  

• Added default values for Environment Settings
  Users will now see recommended settings applied by default on the Environment Settings screen when creating or updating an Environment.

• Enhanced Error logging UI for failed Releases
  In case of a failed release, the error info screen has been revamped to include more contextual information along with the stack trace. Users can also choose to view the Terraform logs directly from this screen.

• Empty screen for logs terminal
  In case there are no logs available, the log terminal will now display an empty screen with the message "No logs available yet".

• Templatized K8s configuration labels
  The Kubernetes configuration file that users can download from the Environment Overview screen is now templatized to name the labels based on environment, user and context.

• Lifetime policy for Artifacts in AWS ECR
  Lifetime policy has been enhanced for Artifacts registered in ECR (Elastic Container Registry) with a maximum cap of 1000 artifacts.

📘

Did you know?

Facets provides the capability to perform rollback to a previously registered artifact from your Control Plane. Learn how to rollback to a previous image in Artifact History and Rollback documentation.

• Added support for Allow Destroy option in Release
  Users can now choose to set a Boolean flag allowDestroy when performing release using REST API. If this flag is set to true, it will allow the destruction of protected resources like Kubernetes clusters, node groups and databases during a release.
• Added support for Helm resources
  Users can now choose resources of type Helm while performing a Selective Release from the Releases page.
• Enhanced maximum Node Count for default Node Pool in GCP to 128
  A new default node pool has been provisioned for GCP with 16,000 IP addresses available with the IP range reserved per node set to 128. This has enhanced the maximum node count to 128 from the previous limit of 16.
• Added support for creating custom Node Pools in GCP
  Users can now create node pools in GCP with custom sizing, taints, labels, node configurations and network configurations. To understand all the properties available when creating a custom node pool, check out the node pool schema on Github.
• Reload Advanced Filters in Notification Subscription
  Added support to reload the Advanced Filters when user is Creating or Updating a Notification Subscription after the user has selected all required options.
• Auto refresh Releases screen when Release is in progress
  The Releases screen will auto-refresh every 30 seconds when a Release or Destroy operation is in progress.

🐞 Bug Fixes

• Fixed a bug where where using the character "$" was causing issues with the Overrides API.
• Fixed a bug where the Sign Off button was not displayed correctly in case no previous releases were signed off in the environment.
• Fixed a bug where Rollback button was enabled for non Admin user in Application Live Release screen.
• Removed a duplicate refresh button in Terraform logs under the Releases screen.
• Fixed a bug where the context switcher was unable to read the name of the Environment in breadcrumb navigation.
• Fixed a bug that was not allowing the UI to preserve the state of the Resource Center after switching context through breadcrumb navigation.
• Fixed a bug where the context switcher was not handling incorrect URLs gracefully.

📚Documentation Updates

• Documentation for Using Webhooks for Notifications has been added to Readme.

---

Release v0.11 was available for use from Monday, 19th September 2022.

v0.11 brings Webhook support for notifications, Refresh command to facetsctl, and lots of enhancements and bug fixes.

✨What's New

• Webhook support for Notifications Integration
  You can now create a Notification Subscription by adding a user defined payload for any Webhook based Channel. This can be done by attaching a custom payload in JSON format with given field attributes as the Notification Message after selecting the appropriate Channel.

• Autocomplete for Webhook Payload editor
  When adding a custom payload as the Notification Message, the fields will be autocompleted based on the Fields list.

• Refresh command added to Facets Command Line Tool implementation
  Users can now use facetsctl refresh command to refresh the Kubernetes Credentials for a specific environment in a defined blueprint. For more information, refer Command Line Tool documentation.
• Application Load Balancers implemented for GCP and AWS
  Users can now implement Load Balancers for AWS and GCP infrastructure by defining it in their blueprints. Additionally, users can also override the domains from the Facets Control Plane to add custom domains and SSL.

📈Enhancements

• Ability to clear selected Continous Delivery Parent
  An option to clear the CD Parent selection is now provided in the CD parent dropdown menu under the Permissions page when creating/editing an Environment.

• Revamped Variables and Secrets screen
  The Variables and Secrets screen has been updated to provide both secrets and variables in a single table, along with giving users the ability to filter by Name or Variable Type.

• Revamped Resource Configuration and Override Configuration pages
  1. The Resource Configuration page has been modified to showcase a diff view of the blueprint definition and the effective configuration. This provides users with a better perspective on what has changed as a result of overridden configurations.
  2. The Override Configuration page for resources has been modified to showcase a side-by-side view of the blueprint definition and the overridden values. This enables users to view the keys that exist in blueprint configuration.

• Added support for Neo4j resources
  Users can now choose resources of type Neo4j while performing a selective Release from the Releases page.

• Improved Logs Terminal
  The Logs terminal has been modified with additional features to improve usability and ease-of-access. Users can now search for phrases inside the logs, as well as copy multiple lines from the logs easily.

• Changed TF Version to IaC Version everywhere
  The keywords TF Version/Terraform Version have been replaced with IaC Version across all labels, tooltips and toaster messages. To know more about managing IaC versions, refer to Manage Infrastructure as Code (IaC) documentation.
• Private support for Load Balances in Azure
  Users can now provision private Load Balancers in Azure by setting the private key to true in their Ingress definition. This enhancement was required since https is not supported in private Load Balancers because “only private IP” mode is not supported in Azure Application Gateway v2 SKU deployments.
• Ability to access MongoDB from VPC
  Users can now access MongoDB from within their Virtual Private Cloud(VPC). This enhancement was added to enable access to MongoDB resources from other machines and other environments in that VPC.
• CloudSQL Postgres enhancements
  Facets provisioned CloudSQL Postgres now supports:
  • Online resizing of disk.
  • Query insights.
  • Configuring a Maintenance window.
  • Creating and editing a Backup configuration.
  • Configuring User supplied labels for the Postgres instances.
• Memorystore Redis enhancements
  Facets provisioned Memorystore Redis now supports:
  • Configuring read only replicas.
  • Configuring a Maintenance window.
• GKE Ingress support for IPv6 addresses
  Facets provisioned GKE Ingress now supports IPv6 addresses. Users can configure this by setting the ipv6_enabled flag as true in the Ingress definition.

🐞 Bug Fixes

• Fixed a bug where empty string or null values were not accepted in Clear CD Parent Selection API calls.
• Fixed a bug where users were not able to run specific commands in Kubernetes jobs.
• Fixed a bug where the stack trace was incorrectly parsed in error logs.
• Fixed a bug where the releases were failing intermittently when checking out the Git repository.
• Fixed a bug where alert callback was incorrectly throwing HTTP 500 exceptions.
• Fixed a bug where ingress pods were not scaling up in case of traffic burst.
• Fixed a bug where users were unable to create Aurora MySQL RDS environment.
• Fixed a bug where releases were picking up Master branch commits in the blueprint which were not signed off.
• Fixed a bug where updating the payload for Subscriptions removed advanced filters.
• Fixed a bug where users were facing unexpected navigation inside Create/Edit Environment screens.
• Fixed a bug where filtering Resources was not working as intended inside context switcher navigation.
• Fixed a bug where the Settings tab in sidebar navigation was not visible after log in.

📚Documentation Updates

• Documentation for Command Line Tool for Facets has been updated.
• Documentation for Managing IaC Versions has been added to Readme.

v0.9 brings IaC Versioning Management, Templates for Blueprint creation, Kubernetes Upgrade to v1.21 for AWS, and lots of enhancements and bug fixes.

✨New Features

• IaC Versioning Management is now available in your Control Plane.
  Users are now able to change IaC Major and Minor versions as well as the stream for the current environment. This can be done from the Environment Overview screen as well as the Release History screen.

• Templates in Blueprint Create page and revamped UI.
  Users can now select pre-defined templates while creating a new blueprint to simplify their first time set up process.

• Kubernetes Upgrade to v1.21 for AWS infrastructure.
  Users can perform an upgrade on their Kubernetes Components to version 1.21 directly from the Control Plane. You can find more information in this document.

• Default Infrastructure settings for all supported Cloud Providers (AWS, GCP, Azure).
  Users can now create base infrastructure which will have the following default values assigned automatically.

• Dropdown options for Regions and Availability Zones.
  Users can now select the regions and AZ for their environment from the latest available regions and AZ in Environment Create and Update screens.

⚖️Enhancements

• Windows applications are now supported as an application resource type.
• All resources have been enhanced to have a cluster tag present on them for easier identification.
• If a user creates a new blueprint, they will now be redirected to a screen prompt to create a new environment.
• Improved exception handling while switching screens in the Control Plane using the context switcher.
• Improved the context switcher navigation by adding necessary parameters when switching context.
• Fixed a bug where the Kubernetes dashboard was not rendering properly due to missing substack.
• Fixed a bug where the release cron was not honouring the input times as UTC.
• Fixed a bug where Prometheus was throwing errors due to incorrect deployment in multi-az environments.
• Fixed a bug where No Loaders were available for selective Releases.
• Fixed a bug where Application Configuration was showing incorrect values.

📚New Documentation

• Documentation on how to Restrict User Access to Environments has been added to Readme.
• Documentation on Optional Filters for Notifications has been added to Readme.
• Documentation on Viewing Persistent Dashboard for K8s events in Grafana has been added to Readme.
• API Reference on how to Override Resource Definition in an Environment has been added to Readme.

v0.8 brings Context Switcher, Optional filters for Notifications, and lots of enhancements and bug fixes.

✨New Features

• Breadcrumb navigation and updated sidebar!
  A breadcrumb has been added to Facets UI that will act as a navigation system with a context switcher through which the user can easily move between different environments and pages. The sidebar has also been updated and new buttons for Settings and Docs have been added for ease of user access.

📘

Want more screen space in your Control Plane?

Click the hamburger icon on the top left of your screen to toggle the sidebar text on/off!

• Restrict Access for Users to specific Environments.
  Users with the ADMIN role can now set user access restrictions for environments using role based access control. You can learn more about this feature in Restrict User Access to Environments.

• UI Buttons disabled based on user role.
  All UI buttons now have a validation check based on user role and permissions to allow/deny actions. For a user who has the relevant permissions, the buttons will be enabled with a tooltip that describes the action performed by the button. If a user does not have the relevant permissions to perform an action, then the button will be disabled with a tooltip stating "Access is forbidden".

• Landing page for new users without any defined Blueprints.
  New users will now see a landing page showcasing a link to create their first blueprint. The landing page also includes a demo video on using Facets Control Plane and a link to the Readme Documentation.

• Optional filters for Notifications
  Users can now add optional filters based on selected notification type while creating or updating any subscription.

• Delete User functionality added to User Management screen.
  Users with the Admin role now have the option to delete a user directly from their Control Plane in the User Management screen. There is also a popup prompt to safeguard against accidental deletion.
• Kubernetes Events are now available as a Persistent Dashboard.
  All Kubernetes events are now persisted in a custom Grafana Dashboard aptly named "Kubernetes Events". You can also filter events in the dashboard based on namespace, kind and name of the object. Click here to learn more about using the Grafana Dashboard with Facets.
• Webhook support for notifications.
  Notifications can now be created via a webhook as configured by the user with the required payload.
• API for Terraform Version Management
  Users can now choose a particular version of Terraform code to deploy their application using this API.
• Native ingress support for GCP load balancers.
  Users can now choose to use GCP native ingress (http(s) loadbalancing) as opposed to the default open source nginx-ingress based solution. This means that users can use Google managed SSL certificates that auto-renews.

⚖️Enhancements

• Environment Create and Update page have been enhanced with additional options and validations for ease of use.
• Environment Overview page has been overhauled and new widgets have been integrated containing relevant information about the Environment Information, Successful Releases, Release Schedule, and Alerts.
• Templates for Blueprint creation have been developed to facilitate a quick start for users, this feature will be added for all users in the upcoming releases.
• New Notification types have been added for creating notification subscriptions.
• The default mode for setting overrides for resources is now using an in built code editor. The notable exception for this is setting overrides for applications, where the user has to toggle from Form mode to Code mode.
• All API endpoints have been enhanced with granular RBAC checks to only be accesible to users with the appropriate permissions.
• Added version history in all pages that have a write action with an option for comparison of the currently registered version with any of the previous 5 versions.
• Added missing permission mappings for RBAC roles.
• Added descriptive error logs for failed releases in the Releases tab.
• Added pagination and filter fields in the Releases tab.
• Fixed a bug where preview popup was not visible for Slack Notifications triggered from the Control Plane.
• Fixed a bug where latest build image was not picked for scheduled deployments.
• Fixed a bug where error message was not visible on trying to delete a non-empty blueprint.
• Fixed an issue with Sidecar configuration injection for Istio.
• Fixed a bug where Template Inputs were not displayed in trash page after deletion.
• Fixed an issue with user navigation to Environment screen without selecting an environment which caused pages to not load with data.
• Fixed some bugs with the UI in Resources page.
• Fixed a bug where the release schedule cron was not calculating the input times in UTC.

📚Documentation updates

• Documentation for Secrets Management has been added to Readme.
• Documentation for External Tools and Using Them has been added to Readme.
• Documentation for Overriding Resources in an Environment has been added to Readme.
• Documentation for Artifacy History and Rollback has been added to Readme.
• Documentation for Rolling Restart of Pods has been added to Readme.
• Documentation on how to Access Wetty from your Control Plane has been added to Readme.

v0.7 brings ability to restore soft deleted entities, validation check for invalid Blueprints, and lots of enhancements and bug fixes.

✨New Features

• Ability to restore soft deleted entities and Trash section
  A new Trash section has been added in the sidebar that lists all the soft deleted entities by the user. This provides users the ability to soft delete unneccesary entities and restore them based on their need.

💡

Currently, Blueprints, Environments and Template Inputs are the valid entities that can be soft deleted and restored from the Trash screen.

• Validation check for invalid Blueprints
  A new error screen has been added in case of failure of validation check for created blueprints before launching an environment. This will help in rectification of errors in case of syntax error in blueprint definition, missing mandatory files or wrong ingress references.

• RBAC assignment at Environment level for users.
  Administrators now have the ability to restrict access to specific Environments to users either during New User creation or from User Management screen. This can be done by choosing from the list of environments in the Restrict Access to Environments dropdown option. Note that this is an optional restriction, and by default the user will be granted access to all Environments.

• Explicit error widgets for Launch Failed, Destroy Failed, and Stopped status.
  Users will now be able to see the exact error in their environment's Tools page, Alerts page and Applications page for different states. This feature has been added for easier identification and rectification of errors.

• Environment Settings can now be updated in the Environment Overview page!
  Users can now change all the default or existing values for an environment based on their blueprint definition, under the settings in the environment overview page.

• Custom parameter can now be enabled for cloud sql Postgres.
  In the postgres-instance JSON, we now support an advanced section where custom database_flags can be set by the user. To learn how to work with flags, check the Google Cloud documentation.
• NAT setup has been enabled for IP whitelisting.
  Facets supports creating kubernetes node groups through blueprint definition. (Node Pool Schema).
  Any nodepool created using this schema results in a private node group being provisioned. All of the outbound traffic can now be routed via a NAT gateway with a static IP address.

❗

️Enabling this results in recreation of GKE cluster in already running environments.

⚖️Enhancements

• When a user creates a new Blueprint, they will now be redirected to the Environment creation screen with a prompt to create a new environment.
• Terraform Error Parsing has been enhanced to parse Error logs and inform users of the error logline. Users can now see the metadata surrounding the error for easier identification.
• Fine Grained Notification Filter API has been changed to a POST request instead of GET. This will enable user to get specific notifications for the necessary object.
• Added Azure Windows node support.
• Elastic Kubernetes Service (EKS) has been upgraded to version 1.21. Read the official release announcement here.
• API call to delete Users from Facets UI has been created, this will simplify user management from the Facets UI for accounts with Administrator permission.
• Blueprint Deletion API has been updated to only allow deletion after checking there are no environments in that blueprint.
• Fixed a bug where Role permissions on hover were showing the wrong information temporarily.
• A Version History page has been added in all pages that allow Override operations, with an option for comparison of the current version with any of the previous 5 versions.
• Action buttons are now enabled based on RBAC roles across all screens in the UI. For more information on RBAC roles in Facets, see Managing Users.
• Fine-grained filter for notifications has been added to show values based on environment name.

📚Documentation updates

• API Reference for Triggering a Release has been added to Readme.
• API Reference for Triggering a HOTFIX Release has been added to Readme.
• Documentation for Granular Roles and Permissions has been added to Readme.

v0.6 brings a new Login page, User Role privileges in a tooltip, rolling restart, and lots of enhancements and bug fixes.

✨New Features

• We have a new Login Page!
  The login page for Facets Control Plane has been revamped keeping a better UX in mind. The login page now supports basic validation for email and also has a hide/show feature for the password field.

📘

Now you can stop obsessing over whether you input the right password and don't need to retype it 4 times!

• Access Privileges of a User Role are now displayed as a tooltip in Create User screen.
  This feature has been added for ease of access of Administrators when creating a New User and assigning roles to them in User Management. On hovering over the infotip, all the permissions associated with that role are made visible.

• Rolling Restart functionality is available for all deployed Pods.
  Users can now perform rolling restarts on all pods in a deployed application.
  A rolling restart will restart all deployed pods one at a time (while keeping the other pods running) until they have all been updated. The primary use case for this is that your cluster can keep functioning and your application will not be affected or go down.

• Two new columns, Registration Type and Registration Value have been added in Artifacts screen
  These columns will functionally replace the Release Stream column. Users can use these two columns to filter artifacts. The filter for Registration Type has a dropdown menu with three list values: All, Release Stream and Environment ID. The filter for Registration Value is a text filter.

📘

Users are now able to add artifacts based on a Release Stream or an Environment ID, hence this feature has been added for easier identification of different types of artifacts in use.

• API call to restore Versioned Objects
  All Versioned Objects can now be restored back to any previous version using Restore APIs.
• API call to Soft Delete Entities
  Users can perform soft deletion of entities (stack, environment, etc.) and restore them back if required using the Soft Delete APIs.

⚖️Enhancements

• Users can now choose any branch in the repository to update their existing blueprint. This can be done through the Edit Action in Blueprints Screen > Branch.
• Fixed a bug where Whitelisted NAT IPs were encountering HTTP 403 and 500 error codes.
• APIs for Fetching Artifact History and Get Artifacts have been reworked to streamline their responses.

v0.5 brings Kubernetes Embedded Dashboard, External Tools screen, Artifact History and Rollback, and lots of enhancements and bug fixes.

✨New Features

• Kubernetes Embedded Dashboard has been integrated into the Facets UI under the Tools page.
  This will allow users to dynamically interact with Kubernetes related actions directly in Facets UI. This also removes the overhead of downloading and refreshing kubeconfig for users who can simply use this embedded dashboard in Facets UI.
  A few use cases for using this dashboard are:
  ‣ Quick access to Logs: Users can live tail the logs of pods.
  ‣ Direct execution: Users are able to execute directly into the Pods with the appropropriate permission and debug from the UI.
  ‣ View pod status and events: Users can see all k8s events, pod status, etc. right from the Facets UI.

  For more information on using the Embedded Dashboard, check out the official documentation.

• A new tab has been added to the Tools page, External Tools which contains a few tools available for use out of the box. Some of the included tools are:
  ◦ Prometheus: Monitoring System and Time series database
  ◦ Alertmanager: Handles alerts sent by client applications such as the Prometheus server.

• Layout changes for Releases Screen
  To streamline the Releases screen and help users perform necessary actions easily, the layout for Releases screen has been modified. The Launch and Destroy buttons are now the primary buttons listed on the top right corner, and all other actions are listed under More Options.

• Added ability to view Artifact History and Rollback to a previous build image
  Users now have the ability to access previous build images for any particular application and make a rollback to their desired version. Currently five previously deployed build images are available for the user to choose for rollback.

⚖️Enhancements

• Removed force delete functionality for clusters. Previously, users were able to force delete live clusters but this functionality has now been removed.

❗️

In case you want to delete a live cluster, contact Facets Support.

• Added detailed error messages across the UI for access denied errors based on RBAC.
• Redis now supports implementation in cluster mode. Previously, only standalone server implementation was supported.
• Postgres intent now supports “cloudsql” flavour in GCP environments. This allows provisioning regional postgres on CloudSQL with write and read replicas.
• Facets EKS clusters now have 12288 IPs available for pods to use. The number has been increased threefold from the previous limit of 4096 IPs.

This page contains the Release Notes for v0.4

✨New Features

• All artifactories are auto selected when creating a new blueprint.
  For more information on creating and registering a Blueprint, check out the Create your first Blueprint page.

• API call to Get Permissions associated with Roles
  This API will enable users to list out all the permissions associated with a given role. Note that the role should exist in the list of predefined roles and have permissions attached to that role.

• API call to Rolling Restart All pods
  On providing applicationName and ClusterId, any role with K8S_DEBUGGER access can now do a rolling restart on all pods. For more information on roles and permission, check out the Managing Users page.

🛠Bug Fixes and Improvements

• GKE auto upgrade has been disabled.
• Prevent failure if credentials requested are invalid, which can happen in case the resource does not exist/ is not supported/is disabled.
• Descriptive Error Message in now thrown for incorrect blueprint name or application name when using Artifact History API.
• Artifact History API will now return the latest registered as the top element of the list.

This page contains the Release Notes for v0.3.

✨New Features

• Prometheus Metrics have been enabled for easy access to business metrics. Prometheus will also create and send alerts if the release for any customer fails more than x time or keeps failing for x hours(configurable).
  The new metrics that can be viewed are:
  - Number of releases via API + cron job.
  - Status of all releases via API + cron job.
  - Expose business metrics for all API endpoints (count, duration. percentile, etc.)

• New feature to Delete Artifact through the UI.
  A new workflow has been created for the Delete button under the Actions column in Artifacts UI screen.
  A confirmation message will popup on clicking the Delete button with a warning message as shown in the image below. On successful deletion of an artifact, the confirmation dialog closes, a success toaster is displayed and the artifact is removed from the list.

🛠Bug Fixes and UI Improvements

• Fixed cached tunnels by adding automatic restart of Control Plane after Cluster Launch to route tunnels.
• Fixed component version being reset on cluster update API call by adding a call to sync the component version if it is empty on cluster update.
• All artifactories are now automatically selected when Creating/Updating the blueprint.