Skip to main content
⏳ Estimated read time: 17 min read

June 2025

StackGen Intent-to-Infrastructure Platform​

With the June 2025 Release, we've enhanced our cloud infrastructure automation platform with the DevOps governance features teams search for most. Our new Cloud Asset Discovery, unified Activity Logs, and Compliance Dashboard deliver the infrastructure visibility and regulatory compliance capabilities growing companies need.

Our latest DevOps productivity enhancements include Backstage integration, automated Module Catalog, and streamlined Infrastructure-as-Code deployment. These cloud management improvements reduce deployment time while maintaining the security and consistency enterprise teams require.

We've resolved critical platform stability issues to deliver the reliable cloud infrastructure automation experience your team depends on. Discover how StackGen's latest capabilities can streamline your DevOps workflow—explore the complete feature guide below.

What's New​

Cloud Asset Discovery in StackGen​

Click to view

We’re excited to introduce Resource Discovery in StackGen — a high-impact feature that simplifies Day 0 visibility into your existing cloud infrastructure and supports ongoing drift detection.

Discovery

How Discovery Works

  1. Pre-appStack Creation: Initial Resource Discovery

    Discovered Resources

    • Import your existing Terraform state files (.tfstate) to visualize cloud resources before creating an appStack.

    • Selectively include resources from the discovery to create a new appStack.

      Discovered Resources

    • Seamlessly update resource selection before finalizing the appStack topology.

  2. Post-appStack Creation: Use Drifts for Continuous Drift Monitoring

    • Detect and track configuration drifts between the deployed infrastructure and your defined Infrastructure as Code (IaC).

    • Easily remediate drift by updating the appStack based on real-time changes in your environment.

      Discovered Resources

How It Helps

  • Day 0 Insight: Visualize your cloud footprint before provisioning or managing with StackGen.
  • Streamlined Onboarding: Accelerate appStack creation using existing infrastructure definitions.
  • Governance-Ready: Maintain alignment between live infrastructure and desired state over time.

StackGen’s Resource Discovery is your first step toward smarter, more resilient infrastructure management.

You can also create appStacks from Cloud Discovery once your discovery is complete. Check out the Cloud Asset Discovery and Drift Detection documentation.

Activity logs: Unified Visibility Across CLI and UI​

Click to view

We’ve introduced Activity logs for your CLI Runs in the CLI Runs tab in StackGen to unify visibility across both the Web UI and the CLI workflows.

CLI Runs

This enhancement ensures that all appStack lifecycle actions, including provisioning and destruction triggered via the CLI, are now seamlessly tracked and displayed in the StackGen UI.

Why this matters:

  • Many teams (DevOps, Engineering) rely on the StackGen CLI for its speed and automation-friendly interface.
  • Previously, actions performed via CLI weren’t visible in the Web UI, creating gaps in auditability, transparency, and collaboration.
  • The CLI Runs tab eliminates this gap by bringing CLI and UI activity into a single, unified view.

With this update, important appStack actions, no matter where they’re triggered, are now traceable, visible, and auditable from one place.

Check out the CLI Runs documentation to know more about Activity Logs.

StackGen Compliance Dashboard​

Click to view

We’re excited to introduce the StackGen Compliance Dashboard, designed to simplify and streamline compliance tracking for your cloud infrastructure.

Compliance Overview

Key Features

  • Visibility into passed and failed policy checks
  • Mapping to control IDs aligned with frameworks like NIST, FedRAMP, and Mars-E
  • CSV export of policy checks for easier collaboration
  • Support for both automatic and custom policy enforcement
  • Audit-ready reporting and continuous compliance tracking

Why It Matters

Compliance reporting no longer needs to be a manual, siloed effort. The StackGen Compliance Dashboard empowers teams to monitor and report on compliance status with confidence.

Get Started: Access the dashboard from the StackGen Home or directly within your appStack.

Stay ahead of audits and security reviews with centralized compliance insights. Check out the Compliance Dashboard documentation to learn more.

Backstage Self-Service: Powered by StackGen​

Click to view

We’re excited to roll out Backstage Self-Service, a seamless way for your developers to scaffold applications and provision infrastructure, without needing to rely on DevOps!

Backstage Self Serve Home

note

This feature is available on request. Contact support@stackgen.com to get started.

What’s Possible?

With StackGen self-service integrated into Backstage, your developers can:

  • Scaffold backend and frontend apps
  • Create appStacks directly from templates
  • Generate and export Infrastructure as Code (IaC)
  • Provision cloud resources like S3, RDS, Helm workloads, and more
  • Use advanced configurations like resource packs and nested resource groups

To explore the full guide and sample templates, refer to the BackStage Self-Service documentation. For questions or setup support, reach out to support@stackgen.com.

Module Catalog​

Click to view

The StackGen Catalog provides DevOps and Admin teams with a powerful platform to manage and enforce the use of Terraform modules within your organization. It allows you to curate trusted modules from multiple sources, ensuring developers only use approved infrastructure configurations and streamlining workflows.

Module Catalog

Key Features

  • Centralized Module Management: Import and manage modules from custom GIT repositories, Terraform registries, and StackGen-generated modules in one platform.
  • Web UI and CLI: Use either the Web UI or the CLI to ingest, list, and search Terraform modules. RBAC Permissions: Control module access and assignment based on RBAC permissions, ensuring only approved modules are used across teams.
  • Module Enforcement: Enforce specific Terraform modules across your organization to ensure consistency and compliance.
  • Sharing Custom Modules Across Teams: You can share custom modules between organizations or teams, allowing for a more streamlined module management process. Custom modules that are shared remain updatable, and new versions will automatically be available for every team that has access to the shared module. This ensures consistency and reduces duplication across teams.

For full details, refer to the StackGen Catalog Page.

What’s Enhanced​

HCL Is Now the Default Format for IaC Exports​

Click to view

Hashicorp configuration language (HCL) is now the default format for Infrastructure as Code (IaC) exports, making it easier to maintain consistency, streamline your CI/CD workflows, and support reusability. You’ll now see HCL pre-selected in the following scenarios:

  • Exporting and deploying built-in resources for AWS, GCP, and Azure.
  • Exporting and deploying custom modules.
  • Creating tfvars with complex types such as list(map(string)) and list(string).
  • Pushing IaC exports to GitHub.

If you are an existing customer and would prefer maintaining your JSON file, please email us at support@stackgen.com, and we can change your preferences from the new default HCL to the previous default JSON.

Improved Multi-Environment Support in IaC​

Click to view

We’ve enhanced the IaC folder structure to simplify the management of multiple environments for your appStacks. Instead of relying on terramate exports and IaC dependencies, StackGen IaC now uses an env directory to generate configurations for each environment profile.

Env Folder

Key improvements include

  • Exporting configurations only for the specific environment profile you specify via a flag, making exports faster and more targeted.
  • Running ILM commands exclusively for the selected profile using the --env-profile flag, thereby streamlining the process and reducing unnecessary actions.

This update helps you manage multi-environment appStacks more efficiently and makes the CLI experience smoother and more intuitive.

Advanced IaC Tab File and Folder Management​

Click to view

We’ve introduced enhanced capabilities in the IaC tab to help you better manage your infrastructure code.

Manage IaC

You can now:

  • Add new files and folders directly within the IaC tab
  • Rename files and folders inline for improved organization
  • Move files and folders to restructure your IaC repository
  • Delete unnecessary files and folders to keep your IaC code clean
  • Search for the relevant file or folder within your IaC

These features provide greater flexibility and control over your Infrastructure as Code, streamlining updates and maintenance without leaving the interface. To enable these capabilities, please reach out to us at support@stackgen.com.

CLI Support for Bulk Module Onboarding via Git Repositories​

Click to view

You can now onboard entire sets of Terraform modules into your StackGen instance using a single CLI command. This is ideal for teams managing large sets of custom modules across multiple cloud environments.

This enhancement streamlines the onboarding process, especially when working with organized Git repositories that contain multiple modules. If your repository includes modules with overlapping or similar names, StackGen provides CLI flags to handle such scenarios and prevent naming conflicts during import.

Refer to the CLI documentation on uploading from Git repositories for full details and usage examples.

Generate Custom Module Linkages Within Imported Tfstates​

Click to view

This release addresses a significant limitation while importing TFstates that were deployed via multi-resource custom modules. Previously, StackGen couldn’t group resources within imported TFstates under their respective custom modules. This update now automatically detects and groups resources based on the custom module names defined in the TFstate.

Custom module linkages

Key Features

  • Custom Module Grouping: While importing a TFstate, StackGen identifies and groups resources that were deployed as part of a custom module, making it easier for you to manage and upgrade versions of those modules.
  • Support for Brownfield TFstates: If you have been using your custom multi-resource modules, this enhancement ensures you can onboard existing (brownfield) TFstates into StackGen without losing the module-abstracted context.
  • Module Recognition Without Management Features: If a custom module hasn’t been added to StackGen, resources will still be grouped under the module name during TFstate import. However, management features such as version tracking or upgrades will only become available once the module is explicitly defined in StackGen.

This enhancement significantly improves your ability to handle imported TFstates, providing better module context and simplifying module management if you’re an existing Terraform user. For more details, refer to the Custom Modules page.

Team Management Experience​

Click to view

Managing teams in StackGen is now faster, clearer, and more self-contained. As an Admin or DevOps, you can manage all aspects of team membership directly from the Team page, no more jumping between views. This update streamlines team operations and improves role visibility and control.

Teams

Key capabilities include

  • Add members to a team with role assignment
  • Remove members from a team
  • Change member roles directly within the Team view
  • Bulk update roles for multiple members

This enhancement simplifies collaboration and helps platform teams maintain clear boundaries and responsibilities across environments. For more details, refer to the StackGen Settings page.

Module Version Enforcement in Governance​

Click to view

You can now enforce the use of specific custom module versions as part of your governance configurations in StackGen. This enhancement provides tighter control over which infrastructure templates teams can access, ensuring consistency, compliance, and reduced configuration drift across environments.

Key capabilities include

  • Define allowed custom module versions within a governance configuration
  • Restrict the usage of outdated or unapproved module versions across teams
  • View available module versions directly in the governance management screen

This update strengthens StackGen’s governance model by giving platform teams precise control over module lifecycle and team-level permissions. For more information, refer to the CLI Guide for enforcing a Resource Restriction Policy.

What’s Fixed​

Create Resource Pack Button Not Visible​

Click to view

While navigating to a topology with a large number of resources, the new pop-up was hiding the Create Resource Pack button, making it impossible to access. On topologies with fewer resources, the button was visible and accessible.

Resource Pack Button missing

We’ve fixed the issue by adjusting the pop-up behavior to ensure the Create Resource Pack button remains visible and accessible regardless of the number of resources in the topology.

Actions Count Not Displaying Immediately After Workload Drag-and-Drop​

Click to view

While creating an EKS appStack and dragging a workload onto the canvas, the Actions count for the workload resource was not displayed. This occurred immediately after the drag-and-drop action. However, the count will appear if you click on the workload resource or refresh the page.

We’ve fixed the issue so that the Actions count is now displayed immediately after dragging and dropping the workload onto the canvas, as expected.

Governance Configs Incorrectly Allowing Assignment to Other Teams ​

Click to view

While creating a governance config within a specific team and attempting to assign it to another team, all teams were displayed as options when clicking the Assign to Team button. This resulted in the action failing while applying the config to another team.

wrong team assignments

We’ve fixed the issue so that governance configs created under a team are now restricted to that team. Other teams will no longer appear as options, and you can now only apply the config within the team in which it was created.

Resource Restriction Policy for Enforcing Resource Versions Is Failing​

Click to view

While applying a resource restriction policy for a specific resource version (using baseId and templateId), the policy was not functioning as expected. The policy was designed to restrict resources to the latest version of aws_s3 and a custom module of type custom_aws_s3, but failed to enforce the versioning correctly.

Resource Restriction Policy Not Applying

We’ve fixed this issue by ensuring that the resource restriction policy correctly applies to the specified version of the resource, using the provided baseId and templateId to enforce the versioning as intended. The policy now correctly restricts the resources and custom modules based on the specific version.

User Role Incorrectly Assigned While Adding Users to Teams​

Click to view

While adding a user to a team from the member select page and assigning them the Admin role, the Developer role was incorrectly applied instead. This caused confusion, as the intended role was not reflected.

We’ve fixed the issue by ensuring that the correct role (Admin) is applied. At the same time, a user is added to a team, resolving the discrepancy and ensuring the role is accurately assigned as expected.

Terramate Generation Failing Due to Recent Changes​

Click to view

Due to recent changes, the Terramate-based environment profile Infrastructure as Code (IaC) was breaking, causing Terramate generation to fail.

We’ve fixed the issue by addressing the changes that caused the failure. The Terramate-based environment profile generation is now functioning as expected, and the issue has been resolved.

Variable Name Updates Do Not Reflect in Environment Profiles​

Click to view

While renaming a variable in one environment profile, the update was not reflected in other linked environment profiles where the variable should be inherited. This caused inconsistencies in variable management, which could lead to misconfigured deployments.

We’ve fixed the issue by ensuring that variable name updates are propagated correctly across all linked environment profiles. Changes to variable names will now be reflected throughout the profiles, maintaining consistency and preventing misconfigurations.

​Blank Canvas and Import Error While Importing Topology JSON​

Click to view

We have fixed an issue where importing a certain topology.json files resulted in a blank canvas with an Error importing the topology message. The problem was caused by connections referencing Resource IDs that didn’t exist in the resource tree, typically from outdated topology files created before a recent feature upgrade. Now, all connection references are properly validated during import, ensuring the topology loads correctly every time.

archive_file Missing from Plan During Run​

Click to view

Previously, the archive_file data resource was disappearing during terraform plan run. This occurred when the expected source file or file path was missing. Terraform doesn’t raise an error in this case; it silently skips the resource.

We have fixed this issue, and the template now works as expected.

Inconsistent Resource Names in AWS Console Due to Missing name Tags​

Click to view

Previously, some AWS services didn’t require a Name parameter, but the Console displays names based on the name tag. When the tag is missing, names appear blank or inconsistent, making resources harder to identify.

We've added guidance under the Logging and Monitoring framework to recommend using name tags for better visibility.

Workspace Icon Reverts on Sidebar Hover Out​

Click to view

Previously, when hovering over the left sidebar, the correct workspace icon was shown. However, once the pointer moved away, the icon reverted to the personal workspace icon, causing confusion.

Workspace error

This issue has now been fixed. The correct workspace icon remains visible even after moving the pointer out of the sidebar.

Not Found Error When Creating Custom Module Version at Team Level​

Click to view

We have fixed the issue you encountered while creating a new version of a custom module from an appStack, which would fail with a Not found error. You were experiencing this issue due to a missing orgId parameter in the version creation API request if the module scope was set to Enterprise.

Now, StackGen correctly handles edge cases based on ownership and sharing status, allowing you to create a module version only when the correct parameters and permissions are in place.

appStack Tag Added on TFState Import​

Click to view

We’ve fixed the issue you were facing while importing a .tfstate file, where StackGen was unintentionally adding a hidden appstack tag to your resources. This tag, originally introduced for ABAC-based IAM enforcement, is no longer needed, but was still being applied, overwriting user-defined values, and was not visible in the UI.

This behavior has now been removed. StackGen no longer auto-adds reserved tags like appstack during a .tfstate import.

Supported Resources​

Click to view

We now support additional Standalone and Grouped AWS resources. Refer to the Supported Resources document to view the complete list.

Last updated on