Release Notes for v1.7.6

Version 1.7.6

This release introduces significant improvements to the F5 Bulk Apply feature, enhancing its resilience, reporting, and user interface. It also retires the internal documentation self-upload pipeline in favor of a centralized platform.

Changed Features

This release includes the following changes.

F5 Bulk Apply HTTP Profile Semantics

The behavior for applying HTTP profiles in bulk to F5 virtual servers has been modified to prevent failures when a profile of the same type already exists.

• Previous Behavior: The operation would fail with F5 API error 01070097 (duplicate profiles) if a virtual server already had an active HTTP-type profile.
• New Behavior: The process now uses replace semantics. It first detaches any existing, non-matching HTTP profile from the virtual server before attaching the new one. This change avoids the 01070097 error and allows for smoother profile updates.
• Scope: This change only affects HTTP-type profiles. Other profile types, such as SSL and TCP, remain untouched during this operation.

F5 Bulk Apply Resilience and Reporting

The bulk apply process has been made more resilient to individual failures, and the API response provides more granular status details.

• Failure Handling: Instead of aborting the entire batch upon encountering an error with a single virtual server, the process now records the failure for that specific server and continues with the rest of the batch.
• API Response: The API response for a bulk apply operation now includes:
  • failedCount: The number of virtual servers that failed to update.
  • failureReason: A message detailing the cause of failures.
• Overall Status: The operation now returns an overall status of failed only if two conditions are met: 1) no virtual servers were successfully updated, and 2) at least one virtual server encountered an error.

F5 Bulk Apply User Interface

The admin user interface for the F5 Bulk Apply feature has been updated to provide clearer and more persistent feedback.

• Status Display: Bulk apply outcome messages are now displayed on the persistent f5ScopeStatus line, rather than the previous hidden legacy scan panel.
• Detailed Outcomes: The UI now reports a detailed summary of the operation, such as "X updated, Y already set, Z failed".
• Error Surfacing: When a failure occurs, the backend failureReason is now displayed in the UI.
• No-Op Handling: Operations that result in zero changes (0 updated / 0 total) are now treated as warnings instead of silent successes.
• Modal Behavior: In the event of any failure during the bulk apply process, the configuration modal will now remain open to allow for review and correction.

Documentation and Pipeline Retirement

The internal pipeline for self-uploading product documentation has been retired to streamline content delivery.

• New Process: All product documentation now flows exclusively through the Specaria platform's version-cut-over event.
• Retired Components:
  • The manual operator script scripts/upload-specaria-docs.ps1 has been deleted.
  • The cloudbuild-specaria-docs.yaml file has been replaced with a minimal no-op stub. This prevents out-of-repository Cloud Build triggers associated with v* tags from failing.
  • The SPECARIA_DOC_API_KEY environment variable and its related endpoints are retired and have been marked as such in documentation.
• IAM Updates:
  • The secretAccessor role is now granted to the active consumer service account (s2r-admin-api-sa@<project>.iam.gserviceaccount.com). It was previously granted to a historical Cloud Build service account.
• Documentation Placeholders:
  • Hardcoded project references in docs/integration/specaria-values.md have been replaced with the generic placeholder <deployment-project-id>.

---

All SOAP-to-REST docs