Merge pull request #9535 from harness/vishal-av-patch-2

Update OIDC support

docs/continuous-delivery/cd-infrastructure/aws-cdk.md

@@ -14,7 +14,7 @@ This topic provides steps on using Harness to provision a target AWS environment
 
 - You can add AWS CDK provisioning steps to Harness Deploy and Custom stage types.
 - You can perform ad hoc provisioning or provision the target environment for a deployment as part of the deployment stage.
-
+- Currently, OIDC connector is not supported AWS CDK plugin.
 ## Demo Video
 
 <DocVideo src="https://www.loom.com/share/5a118a7ace3e49819c697b7131468990?sid=36ae85f0-0a39-4c5c-ba62-0e1a9d52c4de" />

docs/continuous-delivery/deploy-srv-diff-platforms/aws/aws-sam-deployments.md

@@ -33,7 +33,10 @@ For details on AWS support in Harness, including tooling, limitations, and repos
 - Currently, you cannot add artifacts to your Harness SAM service.
 - You can manage whether Harness performs the SAM build within an ephemeral Docker container in a Kubernetes cluster using the `--use-container` option in the Harness SAM Build step. You can manage the Kubernetes settings for these steps as needed. For more information, go to [AWS documentation](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-cli-command-reference-sam-build.html#ref-sam-cli-build-options).
 - Harness doesn't support a controlled AWS SAM Rollback after a deployment pipeline failure occurs. AWS SAM will deploy the lambda function and if it fails during stack creation, cloudformation will roll it back. After a succesful AWS SAM deployment, Harness is not able to initiate a rollback, due to the AWS SAM cli's limitation to trigger rollback on demand.
-- OIDC-enabled AWS connectors are now supported for AWS SAM deployments.
+
+:::info
+Currently OIDC connectors are not supported in AWS SAM deployments. 
+:::
 
 ## Demo Video
 

docs/continuous-delivery/deploy-srv-diff-platforms/serverless/serverless-lambda-cd-quickstart.md

@@ -396,6 +396,10 @@ plugins:
   - serverless-deployment-bucket@latest
 ```
 
+:::info
+Currently, OIDC connectord are **not supported** for Serverless V2 Plugin
+:::
+
 Variables such as `{{.Values.serviceName}}` will be resolved by a corresponding `values.yaml` file that is added in the same place as the manifest. Follow the steps above to add a manifest, but at step 3 select **Values YAML** instead. Here is an example of a `values.yaml` file for the manifest:
 
 ```yaml

docs/continuous-delivery/deploy-srv-diff-platforms/traditional/ssh-ng.md

@@ -88,6 +88,9 @@ Harness includes connectors for all the major artifact repositories. In this exa
 
 ![](static/ssh-ng-171.png)
 
+:::info
+Currently Delegate-based connections are not supported using the OIDC connector for SSH deployments.
+:::
 
 ### Set up artifact location and details
 

docs/continuous-delivery/deploy-srv-diff-platforms/traditional/win-rm-tutorial.md

@@ -34,6 +34,11 @@ Supported security protocols for WinRM include Kerberos and Windows New Technolo
 * Credentials and other details for the EC2 Instance 
   * To configure and authenticate your WinRM credentials by using NTLM, you should have the domain name, username and password for the EC2 instance.
 * To use Harness execution strategies, make sure you should have [IIS service](https://learn.microsoft.com/en-us/iis/application-frameworks/scenario-build-an-aspnet-website-on-iis/configuring-step-1-install-iis-and-asp-net-modules#to-install-iis-and-aspnet-modules-on-windows-server-2012-using-the-ui) installed on your machine.
+
+:::info
+Currently Delegate-based connections are not supported using the OIDC connector for WinRm deployments.
+:::
+
 ## Objectives
 
 You will learn how to: