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

October 2025

We've listed all the Known Issues for the October 2025 release here. Once these issues are resolved in a future release, they will be included under the Bug Fixes section of the Release Notes.

In-ProgressGCP Modules Get Listed Under AWS Resources After Publishing​

Click to view

Summary: When you create and publish a GCP module via the Module Editor, the module incorrectly gets listed under AWS resources instead of GCP resources in the Resources panel.

Cause: The current resource mapping logic supports only AWS resources. As a result, published modules, regardless of the cloud provider are automatically listed under AWS Resources.

Workaround: There is no known workaround to change the view for listing GCP modules under GCP resources list at the moment. However, you can still reference and use the module in your appStack. To avoid confusion, we recommend naming your GCP modules with a GCP prefix until we fix this issue.

In-ProgressNew Policy Versions Are Not Inheriting Terraform and Provider Version Restrictions​

Click to view

Summary: When you create a new version of an existing governance policy, you will notice that the Terraform and Provider version restrictions from the previous version are not populated automatically.

Cause: The version cloning logic currently copies only metadata and rules from the previous policy version, but does not include Terraform and Provider versioning attributes, resulting in missing default values when you create a new version of an existing policy .

Workaround: Currently, there is no known workaround to preserve versioning values for newly created policy versions. You will have to manually re-select the Terraform and Provider version restrictions while creating a new policy version.

In-ProgressGovernance Config Back Button Does Not Return to the Governance Page​

Click to view

Summary: While configuring a new Governance policy, clicking the Back button does not go back to the appStack Governance page. Instead, the Back button becomes disabled and nothing happens.

Cause: The Back button logic is triggered only after progressing beyond the first screen when you're creating a Governance Configuration.

Workaround: To return back to the Governance page, use the Close (×) button to the top-right of the dialog of the New Governance page instead of clicking the Back button.

Last updated on