CLI Local Module Upload, HashiCorp Vault, and Policy UX
The July 2026 weekly v2026.7.9 release adds CLI upload of custom modules from a local directory (--dir) and HashiCorp Vault as an external secret source.
For StackGen core, variables of type any or any(list) render in HCL Expression mode by default and are flagged as Action Required when they have no default. Policy evaluation shows generation prompts on the Evaluation tab (with a path back to Generation), and several policy and catalog UI issues are fixed.
Aiden updates for this release, including LLM gateways, alert sources, Persona Agent, and skills authoring, are in Aiden v2026.7.9.
Explore the sections below to see what's new, enhanced, and fixed in this update.
| Feature | Link | |
|---|---|---|
| What's New | Custom Modules | CLI Local Module Upload |
| Security | HashiCorp Vault External Secret Source | |
| What's Enhanced | Custom Modules | Any-Type Variable Rendering |
| Governance | Policy Generation Prompt on Evaluation | |
| What's Fixed | Governance | Security Policy Evaluation |
| Catalog | Enterprise Catalog Assign Button | |
| UX | Attributes Side Panel Icons |
What's New
CLI Local Module Upload
Click to view
We've added support to upload custom modules from a local directory through the StackGen CLI, using the --dir flag on stackgen upload custom-modules.
Previously, CLI custom module upload required a Git source (repository URL, ref, branch, tag, and related flags). Now, you can upload Terraform module code from a local directory as a blob into StackGen, without first syncing that module into a Git repository.
Key Features
- Local Directory Upload - Pass
--dirwith the path to your local Terraform module. Do not combine--dirwith Git source flags (--repo-url,--ref,--branch,--tag,--subdir,--secret-name). - Direct Catalog Publish - Publish modules into StackGen when the platform is your module source of truth, instead of requiring a Git-backed import path first.
- Module Source Preference - Generated Terraform can reference modules from the StackGen Registry by default. To vendor modules into the generated Terraform directory instead, set Module Source to Local in preferences.
Why It Matters
Teams that keep modules outside a synced Git workflow can still get them into the StackGen catalog and use StackGen as the registry for those modules.
Read more in Upload Custom Modules and Module Catalog.
HashiCorp Vault External Secret Source
Click to view
This is the first version of HashiCorp Vault support. Vault configurations vary; test your auth method, secret paths, and scale before production use. Contact support@stackgen.com or your Customer Service Manager if you need guidance.
We've added HashiCorp Vault as an option when connecting an external secret store.
Previously, external secret stores supported cloud secret managers such as AWS Secrets Manager. Now, you can ingest secrets from HashiCorp Vault as well. This is especially useful for on-prem environments that already store credentials in Vault.
Key Features
- Vault Provider - Choose HashiCorp Vault when you add an external secret store connection.
- Shared Across Products - Once configured, Vault-backed secrets can be used from both StackGen core and Aiden.
- Configure in StackGen Core - Set up the Vault connection in StackGen core secret settings. Aiden uses the same connection after it is configured.
Current Constraints
- First-cut support. Additional Vault scenarios and larger-scale testing are still in progress.
- Connection setup is done in StackGen core today, even when Aiden consumes the secrets.
Why It Matters
On-prem teams that already use Vault can keep secrets in Vault and reference them from StackGen and Aiden, instead of copying them into another store.
Read more in Secret Store.
What's Enhanced
Any-Type Variable Rendering
Click to view
We've enhanced how variables of type any or any(list) render in the attributes experience, and how missing defaults are flagged.
Previously, these open-ended variable types did not default to expression mode, and missing defaults were easier to miss. Now, any and any(list) variables render in HCL Expression mode by default, and variables without a default are flagged as Action Required.
Key Features
- HCL Expression by Default - Variables of type
anyorany(list)render in HCL Expression mode by default. - ui-control Override - Override that default only by explicitly defining a
ui-controlinstackgen.yaml. - Action Required Flag - Variables of type
anyorany(list)that do not have a default value are flagged as Action Required.
Why It Matters
Open-ended module inputs open in the right editor by default, and incomplete any values show up as action items before you move on.
Read more in Custom Module Rendering.
Policy Generation Prompt on Evaluation
Click to view
We've enhanced the Policy Evaluation experience so the generation prompt stays visible, and you can return to Generation when you need to edit it.
Previously, it was easy to lose the prompt that produced a policy once you moved into evaluation. Now, generation prompts are visible on the Evaluation tab, and you can navigate from Evaluation back to the Generation tab to edit the prompt.
Key Features
- Prompt on Evaluation Tab - See the policy generation prompt while you evaluate the policy.
- Return to Generation - Move from the Evaluation tab back to the Generation tab to edit the prompt and continue iterating.
Why It Matters
You can review a policy with the authoring prompt in view, then jump back to Generation without rebuilding the workflow by hand.
Read more in Custom Policies.
What's Fixed
Security Policy Evaluation
Click to view
We fixed an issue where policy evaluation did not work correctly for existing security policies.
Previously, evaluating existing security policies could fail or behave incorrectly. Policy evaluation now works correctly for existing security policies.
Read more in Custom Policies.
Enterprise Catalog Assign Button
Click to view
We fixed an issue where the Assign button used to assign modules to projects in the Enterprise Catalog table did not render correctly.
Previously, the Assign button could fail to display as expected in the Enterprise Catalog table. The Assign button now renders correctly for module-to-project assignment.
Read more in Module Catalog.
Attributes Side Panel Icons
Click to view
We fixed an issue where policy violation and Action Required icons were not fully visible in the attributes side panel.
Previously, those icons could be clipped or hard to see in the attributes panel. Policy violation and Action Required icons are now fully visible in the attributes side panel.
Read more in Custom Module Rendering.