ADDED

• Pipeline view: Component overview skeleton loader

CHANGED

• Project: UI improvements on ElasticSearch logs configuration stepper

• Project: UI improvements for projects list page

FIXED

• Cloud Cost Management: Chart overlapping in small screens

• Pipeline view: Display sometimes the wrong pipeline when switching between components

BREAKING

• Backend: Update api calls to use milliseconds

ADDED

• Backend: Added request_id to error responses. Added a stack trace if Sentry is disabled

• Environments: Ability to clone a component between it's project's envrionments

• Environments: Added Component layer docs link to the environment empty page

CHANGED

• Console: Pagination: increase items per page

• Environments: Close menu after selection through the quick switch

• InfraView: Update empty-states

• Logs: Update empty-state

• Project: Display environment name on project cards

• Project: Updated default icons in projects, environments and components

• TerraformState: Swift provider should now return NotFound error now when the TF state isn't there

FIXED

• Authentication: When the password had errors or was less that 8 characters, the forgot password option was not shown

• Backend: Fixed dformat-go target

• CLI: Fixed the issue with retrier, which was failing when there was no instance of ElasticSearch

• Concourse: Fixed the parsing of Concourse errors and included error information where it was missing

• Console: Fixed catalog repo stack display not updating after refresh

• Environments: Fixed UI regressions and improved animations, chart tooltips, and component overview layout.

• Inventory: Removed the possibility of panic that could happen during inventory resource creation

• Pipelines: Fixed the merging of pipeline variables when the sample file consisted of only a delimiter

• Pipeline view: Display if the pipeline is paused to a user with pipeline read permission

• Pipeline view: Avoid layout shift when refreshing a pipeline

• StackForms: Autocomplete widgets failing validation when adding arbitrary values

• StackForms: Validation error on autocomplete widgets when no form validations are passed

• StackForms: Error alert not showing when config can't be fetched

• StackForms: Autocomplete now supports arbitrary data

• StackForms: Fixed check of the default value of a string widget, in case if its type is invalid (not a string)

• Stackforms: Included error details in validation errors making it easier for a client to fix them

• TerraCost: Used latest TerraCost version where assigning default region for an AWS provider has been fixed

SECURITY

• Backend: Updated Go version to 1.24

• Backend: From now on the password reset link will be expired after being used once

• Backend: Updated go-git to the latest version

Managing applications composed of multiple microservices often requires creating separate projects for each service, such as backend, frontend, and infrastructure.

This approach leads to fragmented management, making it difficult to maintain a unified view of your infrastructure, costs, and deployments. This complexity is further increased when trying to scale or add new services to existing projects.

To address these challenges, we’re excited to introduce Components - a new way to organize and manage your applications more efficiently.

With Components, you can now decouple stacks from projects, allowing a single project to contain multiple, distinct components, each linked to a specific environment and stack.

For example, instead of managing separate projects for different parts of your application, you can now create a single project named Cycloid that includes:

• Cycloid Backend for your API and business logic.

• Cycloid Database for deploying the database that will be used by the Backend

• Cycloid Frontend for the user-facing interface.

With this new architecture you now have a centralized and cohesive view of your entire application, which streamlines workflows by reducing the need to switch between projects.

Thanks to Components you can easily create and scale granular environments, adding new services as needed - without having to refactor or duplicate existing ones.

Components also simplifies management and enhances visibility into resource usage, costs, and deployments across all elements of your application. This means you can focus resources on building and deploying your services instead of managing complex project structures.

A project section completely reimagined

With the components layer, it was necessary to redesign the whole project and environment creation.

Based on customers feedback and discovery calls, we worked on a better user experience to see at a glance, all the information that really matter to users.

The project view is now listing all the environments available with the components that belong to those environments.

We are introducing the component view, with the pipeline directly available on the overview, but also the quick switch to jump into a sibiling component:

We are really excited to see how you will use this awesome feature and how you will evolve your stack around this new granularity !

Don't hesitate to give some feedback through our roadmap section.

How to use the new components ?

With the components layer, we upgraded our stack format to handle this new entity.

Cycloid is still compatible with your current stacks on V3.

In order to use the full potential of components and have multiple components per environment, you will have to migrate your stacks to the V4 format.

For the migration process, we prepared a how-to that you will find in our cookbook.

To get more information about the components concept, check our dedicated documentation on components.

Changelog v6.0.17

• ADDED

  • Components: Adding the component layer

  • InfraView: Improved empty state message for missing TFState files

  • General: Add tracing using Sentry for Backend and Frontend

• FIXED

  • Infraview: Uncaught error while hovering or clicking certain resources

  • Logs: Broken date picker for logs time range

  • Stackforms: Fixed a panic that could occur when TF form variables had invalid module keys

  • API: Fixed error responses returned on OpenAPI errors

  • Environments: Fixed wrong validation being applied for environment canonical when length was less than 3 characters

  • Members: Ensure names with ' and ` are also valid

• ADDED

  • Console: Org menu and workers pop up now can be open in new tab

  • Cost Estimation: module.count is now evaluated

  • Cost Estimation: Add new AWS resources

  • Errors: When an unexpected error happens, "View details" button display in a panel some details about the error to help our support to fix diagnose the issue

  • Service Catalog: Added 'latest' field, displaying whether provided stack is using the latest version

  • Backend: Added support of TLS for Redis and ElasticSearch (and an option to skip it)

• FIXED

  • Console: The filters had issues with the relative time range

  • Cost Estimation: Some attributes passed to the modules were not read correctly and were set as empty while there were having a values

  • External backend: Fixed incorrect ID parsing in some error messages

• CHANGED

  • Backend: Upgrade alpine base image to 3.21 to fix security issues

Changed

• Stackforms: Always display search in dropdown regardless of item count

Fixed

• Stackforms: Disable the possibility to pass free text on the dropdown and behave like an auto-complete widget

You can now search for specific words directly within dropdown menus on StackForms. This improvement makes navigating and selecting options faster and more intuitive.

No need to change your Stackforms configuration files, it will be automatically applied on dropdown widgets that contains more than ten elements.

Changelog v5.1.159

Added

• Console: Change the selection color

• Stackforms: Add search functionality for large dropdowns

Fixed

• Catalog Repository: Fixes the visibility issue where the catalog repository refresh modal doesn't display stack differences

• Credentials: Broken bulk delete label in credentials table.

• InfraPolicies: Fixes the date range error

Changed

• Console: Migrate library momentjs to date-fns

We are addressing a significant user experience challenge in Stacks related to stack sharing and visibility.

Historically, the goal was to foster a community-driven stacks catalog, but with the evolving nature of our product, it's time for a change.

This feature focuses on empowering Stack Authors and Ops with more refined control over stack visibility. Stack Authors can now seamlessly develop and test their stacks without worrying about unwanted sharing, while Ops gain granular control over the visibility of stacks for their users.

We are implementing an inheritance system to make public stacks available only to child organizations, ensuring a more streamlined and controlled sharing environment.

StackForms V3 is now able to use the power of Stack Templating and can read Cycloid builtin variables.

This makes forms even more powerful to write real complex conditions and dynamic fields.

Stack authors can now apply advanced validations for StackForms dropdown widgets, including setting minimum and maximum number of entries in an array, ensuring specific elements exist within an array, and verifying the presence of a key in a map.

These enhancements, configurable directly in the .forms.yml file, are crucial for enforcing precise conditions during form submissions

Check our documentation to test this awesome feature !

In the upcoming roadmap cycle, we're set to introduce a significant improvement to StackForms – the integration of dynamic values in widgets based on user selections.

This expansion beyond existing conditional logic allows Stack Authors to create more interactive and adaptive forms by dynamically updating variables and parameters, including value_ref widget, in response to user input.

Check our documentation to test this awesome feature !

This release introduce a new widget for StackForms that enables users to select a specific number of items from an array using a multi-select dropdown.

This addition aims to address a current limitation in array customization, providing users with the flexibility to curate personalized arrays tailored to their deployment needs.

We're gearing up to introduce Stack Templating, a feature that takes inspiration from the seamless experience of our Bootstrap Stack.

DevOps engineers, brace yourselves for a paradigm shift in stack creation and management. Say farewell to redundant code and complexities as you embark on a journey towards a more intuitive and dynamic infrastructure blueprint.

This new addition promises to simplify the process, reduce redundancy, and amplify the efficiency of your stack management – reminiscent of the user-friendly Bootstrap Stack experience.

Check our documentation

As part of our ongoing efforts to improve the user experience, we will be making changes to the way our application handles projects and environments.

Previously, users were required to create an environment in order to create a project and had to select the environment to view on each tab within the project view.

We have decided to unbind projects and environments, allowing projects to act as containers for multiple environments. Users will now be able to select the environment they wish to explore and all tabs will automatically be scoped to that particular environment.

This enhancement is aimed at streamlining the user experience and providing greater flexibility in managing projects and environments.

Exciting developments are underway as we introduce a new milestone on the path of automation – the integration of a Terraform provider into our platform!

This addition aims to empower users with the ability to create and manage organizations seamlessly, including essential functions like credential management.

One key use case is the introduction of stacks designed for bootstrapping organizations and automating the configuration of Cycloid. This strategic enhancement aligns with our commitment to providing users with robust infrastructure management capabilities.

Check our Terraform Provider documentation