stackgen.yaml Validation, Multiple Auth Providers, and Policy UX
The July 2026 weekly v2026.7.7 release adds a CLI / API path to validate stackgen.yaml when you author custom modules. It also lets you link multiple authentication providers to the same account, and warn clearly when you create secrets from a personal workspace.
For StackGen core, AWS account onboarding is clearer (including access key auth alongside assume role), custom security policy creation keeps more workflow context, and project switching is improved.
Aiden updates for this release, including in-chat help, Slack notifications, Knowledge Hub editing, and the Aiden to StackGen switcher, are in Aiden v2026.7.7.
Explore the sections below to see what's new, enhanced, changed, and fixed in this update.
| Feature | Link | |
|---|---|---|
| What's New | Custom Modules | stackgen.yaml Syntax Validation |
| Auth | Multiple Authentication Providers | |
| Security | Personal Workspace Secrets Warning | |
| What's Enhanced | Governance | Custom Security Policy Creation UX |
| Cloud Accounts | AWS Cloud Account Onboarding | |
| UX | Project Switcher UX | |
| What's Fixed | OCI | appStack-Owned Modules in OCI appStacks |
| Custom Modules | stackgen.yaml Dropdown Controls in Attribute Panel | |
| Cloud Accounts | AWS Credential Handling |
What's New
stackgen.yaml Syntax Validation
Click to view
We've added a CLI / API path to validate StackGen YAML (stackgen.yaml) syntax when you author or update custom modules.
Previously, custom module authors had no dedicated validation endpoint to check StackGen YAML before relying on canvas preview. Now, you can validate stackgen.yaml through the API (and related CLI tooling) to confirm schema keys and structure as you iterate on how the module renders on the canvas.
Key Features
- API Validation - Call a validation endpoint to check
stackgen.yamlprogrammatically during custom module development. - CLI Support - Use the same validation capability from CLI tooling so checks fit the module authoring loop.
- Schema Key Checks - Validation focuses on schema keys and YAML structure for how the module is presented on the canvas (display names, parameters, and related UI).
Current Constraints
- This cut is limited to the API path and to schema keys. It is not full semantic or runtime validation of every canvas behavior.
Why It Matters
Teams that build and maintain custom modules at scale can catch StackGen YAML schema issues through an API, instead of discovering them only after preview or drag-and-drop.
Read more in Custom Module Rendering.
Multiple Authentication Providers
Click to view
We've added support for multiple authentication providers on the same account in both Aiden and StackGen core.
Previously, signing in with Google, GitHub, or another provider could create separate tenants and accounts, which made it painful when a PoC used one identity provider and production needed another. Now, you can associate more than one sign-in method with the same account (for example both Google and GitHub) so the same tenant stays available across providers.
Key Features
- Link Multiple Providers - Connect additional identity providers to an existing account instead of ending up with disconnected tenants.
- Aiden and StackGen Core - The same multi-provider login model applies in Aiden and in the StackGen infrastructure product.
- PoC to Production Continuity - Teams that start on one provider and later standardize on another can keep the same tenant without a separate account migration.
Why It Matters
SaaS customers who change identity providers between evaluation and production can keep one account and tenant, instead of rebuilding access around a second login method.
Read more in Multiple authentication providers on a tenant.
Personal Workspace Secrets Warning
Click to view
We've added a clear warning when you create secrets from a personal workspace.
Previously, you could create secrets in a personal workspace without a strong signal that the location might be wrong for shared or production use. Now, the UI shows an explicit warning in that flow so the scope is obvious before you proceed.
Key Features
- Clear Warning - Creating secrets from a personal workspace surfaces a warning so you confirm scope before the secret is created.
Why It Matters
Teams are less likely to place secrets in a personal workspace when they intended a shared project or org-scoped location.
Read more in Secret Store.
What's Enhanced
Custom Security Policy Creation UX
Click to view
We've enhanced the Create Security Policy workflow so you keep more context while you author and evaluate policies in StackGen core.
Previously, it was easy to lose track of how a policy was produced once you moved into evaluation. Now, the flow preserves workflow context, including the prompts that generated a policy when you evaluate it.
Key Features
- Workflow Context - Stay oriented through the create and evaluate path instead of dropping context between steps.
- Generation Prompt Visibility - When you evaluate a policy, you can see the prompts that created it, which makes review and iteration clearer.
Why It Matters
Platform and security teams iterating on custom policies can see why a policy looks the way it does, then evaluate and refine it without reconstructing the authoring history by hand.
Read more in Custom Policies.
AWS Cloud Account Onboarding
Click to view
We've enhanced AWS cloud account onboarding so required fields are clearer, and you can authenticate with either assume role or access key credentials.
Previously, it was hard to tell which fields were required when onboarding AWS accounts, and access key based auth was not available in StackGen core. Now, the onboarding UX makes the required inputs explicit for each method, and you can use assume role (the original StackGen path) or access key ID and secret access key.
Key Features
- Clearer Required Fields - The UI makes it obvious which fields you must fill for the auth method you choose.
- Assume Role - Continue using StackGen's original assume role flow for AWS account connection.
- Access Key Authentication - Authenticate with access key ID and secret access key in StackGen core, in addition to assume role.
Why It Matters
Teams onboarding cloud accounts spend less time guessing required inputs, and customers who need access key based auth can complete AWS setup inside StackGen core without a separate workaround.
Read more in Secret Store.
Project Switcher UX
Click to view
We've enhanced the project switcher in StackGen core so moving between projects is clearer in day-to-day navigation.
Previously, project switching in the core UI was harder to use in common navigation paths. Now, project switcher interactions are improved for typical project and workspace transitions.
Key Features
- Improved Project Switching - Clearer project switcher behavior for common project and workspace navigation paths.
Current Constraints
- This is a partial implementation. The Personal Workspace path with an existing appStack scenario still needs follow-up work.
Why It Matters
Clearer project switching reduces friction for users who jump across projects while building and reviewing appStacks.
Read more in Navigating UI and StackGen Settings.
What's Fixed
appStack-Owned Modules in OCI appStacks
Click to view
We fixed an issue preventing appStack-owned modules from working correctly in OCI appStacks.
Previously, appStack-owned modules could fail to behave correctly inside OCI appStacks. appStack-owned modules now work correctly in OCI appStacks.
Read more in Edit and Sync appStack-Owned Modules and OCI provider early access.
stackgen.yaml Dropdown Controls in Attribute Panel
Click to view
We fixed an issue where dropdown UI controls defined in stackgen.yaml did not render correctly in the attribute panel.
Previously, dropdown controls declared in StackGen YAML could fail to show as expected when editing module attributes. Dropdown UI controls defined in stackgen.yaml now render correctly in the attribute panel.
Read more in Custom Module Rendering.
AWS Credential Handling
Click to view
We fixed issues in how AWS credentials were handled during cloud account setup and use.
Previously, AWS credential handling could fail or behave incorrectly in onboarding and related flows. AWS credentials are now handled correctly alongside the clearer onboarding UX in this release.
Read more in Secret Store.