News For Dev-ops

Some time ago, I noted that the Process. Standard­Output property is an attractive nuisance because it is valid only on Process objects that you called Start on. You can't just grab any old Process object and try to access its standard handles. Others in the comments had their ideas on how to remove the confusion. Here's mine. The principle is that the properties and methods of the Process object should be valid for all instances of the Process class. If a property or method is valid only conditionally, then either move it to a place that is accessible only if the condition is met, or get rid of it entirely if it adds no value. The standard handles are the three properties that make sense only for Process objects that were created by the static Start method. There are also four methods related to those standard handles, as well as two events. Move them all to a new class, call it Process­ Start­Result : class Process StartResult { public Process Process { get; ...

Network migration teams previously spent days manually reviewing network designs and discovered conflicts only at deployment. AWS Transform now includes two new capabilities that solve both. A new modernization engine goes beyond network mapping to optimize constructs across naming, sizing, security, and structure while surfacing conflicts with existing VPCs already deployed in target accounts. It replaces days of manual review with instant guidance before a single resource provisions in AWS. The service also accepts network configuration files in any format, processing them for migration regardless of source tool or vendor. Before provisioning begins, network teams review and act on modernization recommendations directly or edit any mapped VPC or subnet, retaining full control over the final network design. AWS Transform recommendations include: Splitting VPCs with mixed workload tiers into segmented environments Consolidating constructs fragmented by on-premises hardware co...

Python developers working with Agent Skills can now author skills as files on disk, as inline Python code, or as reusable classes - and mix them freely through composable source classes that handle discovery, filtering, and deduplication. A skill living in your local repository, one installed from your organization's internal package index, and a quick inline bridge you wrote ten minutes ago all plug into the same provider. This is the third post in our Agent Skills series. The first post introduced file-based skills; the second added code-defined skills, script execution, and approval for Python. This post walks through the two additions that complete the picture: class-based skills and multi-source composition . If you've been following the .NET side, the companion post Agent Skills in .NET: Three Ways to Author, One Provider to Run Them covers the same capabilities for C#. Everything shown here is the Python equivalent - same concepts, idiomatic Python API. The scenari...

Amazon CloudWatch Logs Insights query language now supports 13 new commands and functions that give you more powerful ways to query, transform, and analyze your logs. Customers analyzing logs in CloudWatch Logs Insights often need to perform string manipulation, encode or decode field values, parse non-JSON log formats, or calculate geographic distances, so they can derive deeper insights from their logs. With this launch, CloudWatch Logs Insights provides new string and numeric functions (round, startswith, endswith, case, regex_replace, haversine), encoding and decoding functions (urlencode, urldecode, base64encode, base64decode), and new parse and analysis commands (parse logfmt, expand, relevantfields). You can now filter logs by string prefixes, decode Base64 payloads inline, parse logfmt structured logs into fields, expand nested JSON arrays into individual records, calculate distances between coordinates, and automatically surface relevant fields in high-cardinality log groups...

Amazon SageMaker Unified Studio now supports automatic creation of connections for Glue job retries across subnets to improve data pipeline resilience. This helps organizations running business-critical data pipelines reduce unplanned downtime and meet their SLAs — without requiring engineers to manually configure backup connectors or intervene during subnet failures. With this launch, SageMaker Unified Studio automates the provisioning of Glue connectors across subnets defined in the domain VPC configuration. Administrators can define their domain VPC with multiple private subnets across availability zones, and the system provisions the connectors needed for all new projects so that failed jobs can be retried on an alternate subnet automatically. If a Glue job fails because the primary subnet is unavailable due to IP address exhaustion or availability zone degradation, the job can be retried on a connector in a different subnet. No user action is needed beyond the initial VPC config...

We're excited to announce that the PowerShell packages for macOS are now properly notarized and hardened, meeting both Apple's security requirements and Microsoft's internal compliance standards. This has been one of the most consistently requested improvements from our macOS community, and we're glad to finally deliver it. What changed Starting with the next release, the PowerShell .pkg installer and tarball for macOS are: Notarized by Apple — macOS no longer warns you that PowerShell is from an unidentified developer Hardened — the PowerShell binary and its libraries are built with the security entitlements Apple recommends for distributed software This update also includes a fix that properly sets the file permissions on files contained in the tarball. These fixes are included in the next maintenance releases of PowerShell 7.4 and higher. What this means for you If you've been working around Gatekeeper warnings, adjusting security settings, runn...