Revert "Adding Highlights for CDSH 2.36.0"

This reverts commit af825bc.

Author: edgarulg

content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-36-0-rc4.md

@@ -2,7 +2,7 @@
 title: v2.36.0-rc4 Armory Continuous Deployment Release (Spinnaker™ v1.36.1)
 toc_hide: true
 date: 2025-02-05
-version: 2.36.0
+version: <!-- version in 00.00.00 format ex 02.23.01 for sorting, grouping -->
 description: >
   Release notes for Armory Continuous Deployment v2.36.0-rc4. A beta release is not meant for installation in production environments.
 
@@ -47,146 +47,6 @@ Armory scans the codebase as we develop and release software. Contact your Armor
 
 ## Highlighted updates
 
-### Java upgrades 
-
-Java 17 is now the default source and target. Java 11 support has been removed entirely. Please note you may need to add the following JAVA_OPTS options: `--add-exports=java.base/sun.security.x509=ALL-UNNAMED --add-exports=java.base/sun.security.pkcs=ALL-UNNAMED --add-exports=java.base/sun.security.rsa=ALL-UNNAMED` to clouddriver if using GCP accounts due to credentials parsing of certificates. These can set in the [service-settings config](https://spinnaker.io/docs/reference/halyard/custom/#custom-service-settings) . These configs are likely to be added to the defaults in all future releases
-
-{{< highlight yaml "linenos=table,hl_lines=10" >}}
-apiVersion: spinnaker.armory.io/v1alpha2
-kind: SpinnakerService
-metadata:
-  name: spinnaker
-spec:
-  spinnakerConfig:
-    service-settings:
-      clouddriver: 
-        env:
-          JAVA_OPTS: "--add-exports=java.base/sun.security.x509=ALL-UNNAMED --add-exports=java.base/sun.security.pkcs=ALL-UNNAMED --add-exports=java.base/sun.security.rsa=ALL-UNNAMED"
-{{< /highlight >}}
-
-### Enhanced pipeline batch update feature
-
-#### Gate
-
-Adds a new enpdoint, `POST /pipelines/bulksave`, which can take a list of pipeline configurations to save. The endpoint will return a response that indicates how many of the saves were successful, how many failed, and what the failures are. The structure is
-
-'''
-[
-   "successful_pipelines_count"  : <int>,
-   "successful_pipelines"        : <List<String>>,
-   "failed_pipelines_count"      : <int>,
-   "failed_pipelines"            : <List<Map<String, Object>>>
-]
-'''
-
-There are a few config knobs which control some bulk save functionality. The gate endpoint invokes an orca asynchronous process to manage saving the pipelines and polls until the orca operations are complete.
-
-'''
-controller:
-  pipeline:
-    bulksave:
-      # the max number of times gate will poll orca to check for task status
-      max-polls-for-task-completion: <int>
-      # the interval at which gate will poll orca.
-      taskCompletionCheckIntervalMs: <int>
-'''
-
-#### Orca
-
-Updates Orca’s SavePipelineTask to support bulk saves using the updated functionality in the front50 bulk save endpoint.
-
-With https://github.com/spinnaker/orca/pull/4781, keys from the stage context’s outputs section can now be removed (there by reducing the context size significantly). At present the following tasks support this feature:
-
-* PromoteManifestKatoOutputsTask
-* WaitOnJobCompletionTask
-* ResolveDeploySourceManifestTask
-* BindProducedArtifactsTask
-
-
-The PR https://github.com/spinnaker/orca/pull/4788 introduced a new CheckIfApplicationExists task that is added to various pipeline stages to check if the application defined in the pipeline stage context is known to front50 and/or clouddriver. The following config knobs are provided so that all of these stages can be individually configured to not perform this check if needed. Default value is set to false for all of them.
-
-{{< highlight yaml "linenos=table,hl_lines=9-28" >}}
-apiVersion: spinnaker.armory.io/v1alpha2
-kind: SpinnakerService
-metadata:
-  name: spinnaker
-spec:
-  spinnakerConfig:
-    profiles:
-      orca:
-        tasks:
-          clouddriver:
-            promoteManifestKatoOutputsTask:
-              excludeKeysFromOutputs:
-              - outputs.createdArtifacts
-              - outputs.manifests
-              - outputs.boundArtifacts
-            waitOnJobCompletionTask:
-              excludeKeysFromOutputs:
-              - jobStatus
-              - completionDetails
-            resolveDeploySourceManifestTask:
-              excludeKeysFromOutputs:
-              - manifests
-              - requiredArtifacts
-              - optionalArtifacts
-          core:
-            bindProducedArtifactsTask:
-              excludeKeysFromOutputs:
-              - artifacts
-{{< /highlight >}}
-
-Separate config knobs are also provided at the AbstractCheckIfApplicationExistsTask level to determine if clouddriver needs to be queried for the application or not. It is by default set to true, so it is an opt-out capability. the config property is:
-
-'''
-tasks:
-  clouddriver:
-    checkIfApplicationExistsTask:
-      checkClouddriver: false   # default is true
-'''
-
-This feature runs in audit mode by default which means if checkIfApplicationExistsTask finds no application, a warning message is logged. But when audit mode is disabled through the following property, pipelines fail if application is not found:
-
-'''
-tasks:
-    clouddriver:
-      checkIfApplicationExistsTask:
-        auditModeEnabled: false  # default is true
-'''
-
-#### Front50
-
-Batch update operation in front50 is now atomic. Deserialization issues are addressed.
-Configurable controls are added to decide whether cache should be refreshed while checking for duplicate pipelines:
-
-{{< highlight yaml "linenos=table,hl_lines=9-12" >}}
-apiVersion: spinnaker.armory.io/v1alpha2
-kind: SpinnakerService
-metadata:
-  name: spinnaker
-spec:
-  spinnakerConfig:
-    profiles:
-      front50:
-        controller:
-          pipeline:
-            save:
-              refreshCacheOnDuplicatesCheck: false // default is true 
-{{< /highlight >}}
-
-Batch update call now responds with a status of succeeded and failed pipelines info. The response will be a map containing information in the following format:
-
-'''
-[
-    "successful_pipelines_count"  : <int>,
-    "successful_pipelines"        : <List<String>>,
-    "failed_pipelines_count"      : <int>,
-    "failed_pipelines"            : <List<Map<String, Object>>> 
-]
-'''
-
-Here the value for `successful_pipelines` is the list of successful pipeline names whereas the value for `failed_pipelines` is the list of failed pipelines expressed as maps.
-
 <!--
 Each item category (such as UI) under here should be an h3 (###). List the following info that service owners should be able to provide:
 - Major changes or new features we want to call out for Armory and OSS. Changes should be grouped under end user understandable sections. For example, instead of Deck, use UI. Instead of Fiat, use Permissions.