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

July 2025

We've listed all the Known Issues for the July 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-ProgressCreating appstack From Discovery Does Not Include All Resources​

Click to view

Summary: While creating an appStack from a discovery, only the resources selected during the initial appStack creation are included, rather than all the resources available in the uploaded tfstate file.

Cause: The discovery process is incorrectly referencing only the selected resources from the initial appStack creation, rather than importing all available resources from the tfstate file.

Workaround: Currently, the workaround is to ensure all desired resources are selected while creating the appStack from the discovery pane.

In-ProgressModule Editor AI is Generating Deprecated Values in IaC​

Click to view

Summary: While using the module editor to create modules, the AI sometimes generates deprecated values in the IaC, causing issues while running Terraform commands like init, plan, and apply.

Cause: The AI occasionally uses older, deprecated values instead of the latest supported ones, leading to Terraform errors and warnings.

Workaround: Manually update the deprecated values in the exported IaC files before running Terraform commands. Refer to the latest Terraform documentation for supported values.

In-ProgressPartial Resource Provision Or Destruction Not Reported Correctly in CLI Output​

Click to view

Summary: While running stackgen provision or stackgen destroy, if the underlying IAC engine (Tofu or Terraform) fails partly in applying changes (e.g., fails on the 6th of 10 resources), the CLI only reports a general failure error. It does not inform the user that some resources were successfully created or destroyed prior to the failure. This can cause a misleading perception that the entire operation failed without any changes.

Cause: The CLI currently reports only the final status of the stackgen provision or stackgen destroy commands without parsing or presenting partial apply state or intermediate logs from Terraform or Tofu. As a result, users are unaware of partial success or failure unless they manually inspect the state file or backend.

Workaround: After any failed stackgen provision or stackgen destroy, run:

tofu show

or

terraform show

This will show you the resources in your state file in case of stackgen provision and ones that are yet to be destroyed in case of stackgen destroy.

In-Progressstackgen drift detect Command Executes on Archived appStacks​

Click to view

Summary: The drift detect command currently runs even when the target appStack is archived. Archived appStacks are expected to be inactive, and operational commands like drift detect should be restricted. Allowing drift checks on archived appStacks may lead to confusion and unintended operations.

Cause: The CLI/API does not validate the appStack's archived status before executing the drift detect command. As a result, the command proceeds even when the appStack should be considered inactive.

Workaround: Until a fix is implemented, you must manually avoid running the drift detect command on archived appStacks.

In-ProgressPolicies Not Added to appstacks Created via CLI​

Click to view

Summary: While creating appStacks using the stackgen appstack create CLI command, no policies are added to the appStack, even though default policies are expected to be attached based on the selected cloud provider (AWS, GCP, Azure). This leads to a mismatch in behavior between appStacks created via CLI and those created through the UI.

Cause: The CLI did not trigger the default policy attachment logic during appStack creation. This resulted in policy-less appStacks, which may cause security compliance issues or unexpected behavior in downstream workflows.

Workaround: There is currently no workaround in existing CLI versions. To ensure default policies are added:

  • Update to CLI version v0.64.3, where this issue has been fixed.

  • In this version, default policies are automatically attached during appStack creation unless explicitly skipped using:

    --skip-policies

If you are using older CLI versions should upgrade to receive this fix.

Last updated on