✨Environment-Level Secrets, Pipeline History Improvements, and UX Enhancements

This week, we're excited to share several powerful updates that enhance security, streamline your workflow, and improve operational visibility. From environment-level credential management to quality-of-life improvements in pipeline building, these features are designed to make your Maia Foundation experience more efficient and secure. For a full list of recent changes, be sure to check our changelog updates.

🔐 Environment-level secrets and OAuths

We've released environment-level secrets and OAuths, delivering enhanced security and simplified credential management across your data pipelines. This major update provides several key benefits:

• Granular control over sensitive credentials: Secret mapping in the vault is now bound to specific environments. This reduces the risk of accidentally modifying production secrets or OAuths.
• Simplified cross-environment credentials: Secret definitions and OAuths automatically adjust based on environment.
• Ability to edit existing secrets and OAuths: You can now update all secrets or OAuths, making credential rotation much easier.
• Consolidated Public API: We've simplified credential management into a single connections endpoint, moving toward unified management of all credentials under one umbrella.

🎯 Copying and pasting components made smoother

We've ironed out a friction point in the pipeline building process to make your workflow even smoother. Previously, when copying and pasting multiple components, the newly pasted items were not automatically selected.

Now, all pasted components are automatically pre-selected, allowing for immediate movement the moment they hit the canvas. This small change reduces manual effort and keeps your momentum going while building complex pipelines, making the development process more intuitive and efficient.

🚀 Pipeline run history now includes artifact versions

We've shipped an update to the pipeline run history view that makes operational triage faster and more efficient for data teams.

Key improvements include:

• Artifact version is now visible - You can see exactly which version was executed. When you're debugging a failure, you'll immediately know whether it happened before or after a recent change, without having to cross-reference Git history.
• "Triggered by" replaces "Started by" - The column now shows what fired the run (a schedule, a manual run by a user, or the API).
• Time columns are cleaner - Started at, Ended at, and Duration are now separate columns.
• Full folder paths are included in the pipeline detail.

The combination of artifact version and schedule trigger means you can answer two of the most common questions — which version of the pipeline ran and what triggered it — directly from the run history list, without clicking into individual runs.

👀 Artifacts tab more detailed than ever

The Artifacts tab in your project now shows the name of the user who created each artifact and, if you have your own Git repository linked to the Maia Foiundation, the Git commit hash used to create it.

This update makes it easier to trace your artifacts and cross-reference them with your Git history for more context.

💬 We'd Love to Hear From You!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

Want to get involved?

Join the Matillion Community to stay up to date, share feedback, and help shape our product roadmap for future innovations.