From 2ff0d1560cfe44e401939e84af6b72ae79e908ec Mon Sep 17 00:00:00 2001 From: Trece Wicklander-Bryant Date: Tue, 13 Jan 2026 08:43:12 -0800 Subject: [PATCH 1/2] docs: Updates N1 Changelog Regarding API Field Conf_Path --- content/nginx-one-console/changelog.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/content/nginx-one-console/changelog.md b/content/nginx-one-console/changelog.md index f6401eeda..3b1fcc4dd 100644 --- a/content/nginx-one-console/changelog.md +++ b/content/nginx-one-console/changelog.md @@ -9,6 +9,15 @@ nd-docs: DOCS-1394 Stay up-to-date with what's new and improved in the F5 NGINX One Console. +## January 13, 2026 + +### API behavior change: conf_path is now optional for PUT/PATCH operations + +- The `conf_path` field is now optional when updating configurations for NGINX instances and Config Sync Groups via PUT and PATCH operations. +- When `conf_path` is omitted, the system automatically uses the `conf_path` from the existing instance or Config Sync Group metadata. +- When `conf_path` is provided, it must be an absolute path that references a file present in the provided `configs` array. Providing an invalid path or a path not found in the configs returns a `400 Bad Request` error. +- This is a non-breaking change; existing requests that include `conf_path` will continue to work as before. + ## November 25, 2025 ### Observability: Usage metrics data now available for Config Sync Groups From 32edf172582fda545cc6060867399bf4c44ca3da Mon Sep 17 00:00:00 2001 From: Trece Wicklander-Bryant Date: Tue, 13 Jan 2026 12:02:07 -0800 Subject: [PATCH 2/2] chore: Addresses Feedback --- content/nginx-one-console/changelog.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/nginx-one-console/changelog.md b/content/nginx-one-console/changelog.md index 3b1fcc4dd..67f9aa639 100644 --- a/content/nginx-one-console/changelog.md +++ b/content/nginx-one-console/changelog.md @@ -13,8 +13,8 @@ Stay up-to-date with what's new and improved in the F5 NGINX One Console. ### API behavior change: conf_path is now optional for PUT/PATCH operations -- The `conf_path` field is now optional when updating configurations for NGINX instances and Config Sync Groups via PUT and PATCH operations. -- When `conf_path` is omitted, the system automatically uses the `conf_path` from the existing instance or Config Sync Group metadata. +- The `conf_path` field is now optional when updating configurations for NGINX instances, Config Sync Groups, and Staged Configs with PUT and PATCH operations. +- When `conf_path` is omitted, the system automatically uses the `conf_path` from the existing instance, Config Sync Group, or Staged Config metadata. - When `conf_path` is provided, it must be an absolute path that references a file present in the provided `configs` array. Providing an invalid path or a path not found in the configs returns a `400 Bad Request` error. - This is a non-breaking change; existing requests that include `conf_path` will continue to work as before.