Merge main

Author: theunrepentantgeek

.devcontainer/Dockerfile

@@ -1,7 +1,7 @@
 # See here for image contents: https://github.com/devcontainers/images/blob/main/src/go/.devcontainer/Dockerfile
 
 # This is pinned to a particular version of go:
-FROM mcr.microsoft.com/devcontainers/go:1.24
+FROM mcr.microsoft.com/devcontainers/go:1.25
 
 # https://docs.docker.com/engine/reference/builder/#automatic-platform-args-in-the-global-scope
 

.devcontainer/install-dependencies.sh

@@ -94,7 +94,7 @@ fi
 
 # Ensure we have the right version of GO
 
-#doc# | Go | 1.23 | https://golang.org/doc/install #
+#doc# | Go | 1.25 | https://golang.org/doc/install #
 if ! command -v go > /dev/null 2>&1; then
     write-error "Go must be installed manually; see https://golang.org/doc/install"
     exit 1
@@ -104,7 +104,7 @@ GOVER=$(go version)
 write-info "Go version: ${GOVER[*]}"
 
 GOVERREGEX=".*go1.([0-9]+).([0-9]+).*"
-GOVERREQUIRED="go1.24.*"
+GOVERREQUIRED="go1.25.*"
 GOVERACTUAL=$(go version | { read _ _ ver _; echo "$ver"; })
 
 if ! [[ $GOVERACTUAL =~ $GOVERREGEX ]]; then
@@ -113,7 +113,7 @@ if ! [[ $GOVERACTUAL =~ $GOVERREGEX ]]; then
 fi
 
 GOMINORVER="${BASH_REMATCH[1]}"
-GOMINORREQUIRED=24
+GOMINORREQUIRED=25
 
 # We allow for Go versions above the min version, but prevent versions below. This is safe given Go's back-compat guarantees
 if ! [[ $GOMINORVER -ge $GOMINORREQUIRED ]]; then

.github/workflows/deploy-site.yml

@@ -5,6 +5,14 @@ on:
       - main
     paths:
       - "docs/**"
+
+  workflow_dispatch:
+    # no content, allows manual triggering
+
+  schedule:
+    # 5:35 pm every Sunday (UTC)
+    # to ensure the site is rebuilt weekly to publish scheduled blog posts
+    - cron: "35 17 * * 0"
 
 jobs:
   deploy-site:

ROADMAP.md

@@ -10,11 +10,11 @@ Our current release plan:
 
 | Version                                                                |   Estimated Release |
 | ---------------------------------------------------------------------- | ------------------: |
-| [2.16.0](https://github.com/Azure/azure-service-operator/milestone/35) |    Mid October 2025 |
-| [2.17.0](https://github.com/Azure/azure-service-operator/milestone/36) | Early December 2025 |
 | [2.18.0](https://github.com/Azure/azure-service-operator/milestone/37) | Early February 2026 |
-| 2.19.0                                                                 |      Mid April 2026 |
-| 2.20.0                                                                 |       Mid June 2026 |
+| [2.19.0](https://github.com/Azure/azure-service-operator/milestone/38) |      Mid April 2026 |
+| [2.20.0](https://github.com/Azure/azure-service-operator/milestone/39) |       Mid June 2026 |
+| 2.21.0                                                                 |     Mid August 2026 |
+| 2.22.0                                                                 |    Mid October 2026 |
 
 Where linked, versions go to a list of feature and bugs that are planned to be included in that release.
 
@@ -32,6 +32,8 @@ Official releases of ASO v2:
 
 | Version                                                                        |     Release Date |                                                                                        |
 | ------------------------------------------------------------------------------ | ---------------: | -------------------------------------------------------------------------------------- |
+| [2.17.0](https://github.com/Azure/azure-service-operator/milestone/36)         |  8 December 2025 | Release cycle was abbreviated to get key items out before the 2025/2026 holiday season |
+| [2.16.0](https://github.com/Azure/azure-service-operator/milestone/35)         |  22 October 2025 |
 | [2.15.0](https://github.com/Azure/azure-service-operator/releases/tag/v2.15.0) |   20 August 2025 |                                                                                        |
 | [2.14.0](https://github.com/Azure/azure-service-operator/releases/tag/v2.14.0) |     24 June 2025 |                                                                                        |
 | [2.13.0](https://github.com/Azure/azure-service-operator/releases/tag/v2.13.0) |    23 April 2025 |                                                                                        |

Taskfile.yml

@@ -718,7 +718,7 @@ tasks:
       - generator:build
     sources:
       - ./bin/{{.GENERATOR_APP}}
-      - v2/azure-arm.yaml
+      - azure-arm.yaml
       - ../docs/hugo/content/reference
     cmds:
       - ./bin/{{.GENERATOR_APP}} gen-types azure-arm.yaml

…o/content/blogs/release-notes-v2.16.0.md …logs/2025-10-29-release-notes-v2.16.0.mddocs/hugo/content/blogs/release-notes-v2.16.0.md renamed to docs/hugo/content/blogs/2025-10-29-release-notes-v2.16.0.md docs/hugo/content/blogs/release-notes-v2.16.0.md renamed to docs/hugo/content/blogs/2025-10-29-release-notes-v2.16.0.md

@@ -0,0 +1,78 @@
+---
+title: "Developer Talks - Quality of Life Features with Bevan"
+date: 2025-12-19
+draft: false
+description: "Bevan goes over some recent and upcoming features in ASO and how they contribute to a better user experience."
+type: blog
+---
+
+With the release of ASO v2.17 coming soon, this felt like a great time to go behind the curtain and get a better idea of what us devs have been working on, both landed and upcoming, and how they contribute to a smoother user experience for ASO users.
+
+We'll go over two exciting features, one landing in v2.17 and one that shipped in v2.16. Alongside our other host of improvements, we hope these features make using ASO that much smoother for our users.
+
+## Improved error handling for resources that can't be deleted
+
+PR [#4987](https://github.com/Azure/azure-service-operator/pull/4987) landing in v2.17 helps with error handling for Azure resources that can not be deleted directly. Azure hosts a number of resource types that cannot be deleted directly; instead, you have to delete their parents.
+
+If a user does attempt to delete one of these resources directly, they'll be met with a number of noisy errors that will populate in their logs.
+
+A snippet of such an error would look like is below:
+
+```go
+test_logger.go:160: [2024-04-28T22:19:01Z] SqlDatabaseThroughputSettingController 
+    "msg"="Error during Delete" 
+    "err"="deleting resource "/subscriptions/<sub_id>/resourceGroups/<rg_name>/providers/Microsoft.DocumentDB/databaseAccounts/sample-sqldb-account/sqlDatabases/sample-sql-db/throughputSettings/default": DELETE https://management.azure.com/subscriptions/<sub_id>/resourceGroups/<rg_name>/providers/Microsoft.DocumentDB/databaseAccounts/sample-sqldb-account/sqlDatabases/sample-sql-db/throughputSettings/default
+    --------------------------------------------------------------------------------
+    RESPONSE 405: 405 Method Not Allowed
+    ERROR CODE: MethodNotAllowed
+    --------------------------------------------------------------------------------
+    {
+      "code": "MethodNotAllowed",
+      "message": "Message: The requested verb is not supported."
+    }
+    --------------------------------------------------------------------------------
+    " name="sample-sql-throughput" 
+    namespace="aso-test-samples-creationanddeletion-test-sqldatabase-v1a-7e1fc" 
+    azureName="default" 
+    action="BeginDelete"
+```
+
+With this new enhancement, the workflow in ASO is enhanced to detect when a resource can not be deleted directly, return a more informative error message than what you would see previously, and provides details on how to unblock the resource deletion.
+
+## Allowing specification of role assignments by using well-known names
+
+[This feature](https://github.com/Azure/azure-service-operator/pull/4923) builds upon the support of well-known names added in [#4922](https://github.com/Azure/azure-service-operator/pull/4922) and allows users to specify RoleAssignments using the well-known name of a [built-in RoleDefinition](https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles) instead of the full ARM ID.
+
+Before this change if I wanted to assign the "Contributor" role, it would require something like this, using the published GUID:
+
+```yaml
+apiVersion: authorization.azure.com/v1api20200801preview
+kind: RoleAssignment
+metadata:
+  name: aso-sample-contributor
+  namespace: default
+spec:
+  ...
+  roleDefinitionReference:
+    armId: /subscriptions/00000000-0000-0000-0000-000000000000/providers/Microsoft.Authorization/roleDefinitions/b24988ac-6180-42a0-ab88-20f7382dd24c
+```
+
+Now, with this change, I'd be able to use the well known name `contributor` instead:
+
+```yaml
+apiVersion: authorization.azure.com/v1api20200801preview
+kind: RoleAssignment
+metadata:
+  name: aso-sample-contributor
+  namespace: default
+spec:
+  ...
+  roleDefinitionReference:
+    wellKnownName: Contributor
+```
+
+## v2.17 Release
+
+v2.17 introduces these features and more, as we continually strive to make ASO work better for our users!
+
+If you have an enhancement you would like to see in future iterations of ASO, please [submit an issue](https://github.com/Azure/azure-service-operator/issues) or visit the [contributing guide](https://azure.github.io/azure-service-operator/contributing/).