[META] Add Windows Support

[dblock]

Is your feature request related to a problem?

Coming from opensearch-project/opensearch-build#33. In order to release a Windows x64 distribution each plugin needs to work on Windows and include tools that are windows-specific as replacements for any bash scripts.

What solution would you like?

Every component has passing CI on Windows (windows-latest on GHA), including unit, integration and bcw tests, and has Windows-specific documentation, if needed.

• Add Windows CI on pull requests OpenSearch#1448
• Add Windows CI OpenSearch-Dashboards#2451
• Add Windows Support alerting#214
• Add Windows Support anomaly-detection-dashboards-plugin#104
• Add Windows Support anomaly-detection#274
• Add Windows Support asynchronous-search#51
• Add Windows Support dashboards-notebooks#91
• Add Windows Support reporting#191
• Add Windows Support dashboards-visualizations#33
• Add Windows Support index-management-dashboards-plugin#114
• Add Windows Support index-management#172
• Add Windows Support job-scheduler#75
• Add Windows Support k-NN#157
• Add Windows Support notifications#358
• Add Windows Support performance-analyzer#75
• Add Windows Support security-dashboards-plugin#845
• Add Windows Support security#1474
• Add Windows Support sql#249
• Add Windows Support observability#160
• Add Windows Support cross-cluster-replication#220
• Add Windows Support ml-commons#361
• Add Windows Support geospatial#158
• Add Windows Support dashboards-maps#55
• Add Windows Support common-utils#256
• [FEATURE] Add Windows Support  security-analytics-dashboards-plugin#33
• [FEATURE]Add Windows Support security-analytics#86
• [FEATURE] Add Windows Support  neural-search#39
• [FEATURE] Add Windows Support dashboards-search-relevance#16

Example PR: opensearch-project/index-management#210

[dblock]

OpenSearch Windows CI: opensearch-project/OpenSearch#1448
OpenSearch Dashboards Windows CI: opensearch-project/OpenSearch-Dashboards#2451

[peterzhuamazon]

Add geospatial, dashboards-maps, common-utils:

opensearch-project/geospatial#158
opensearch-project/dashboards-maps#55
opensearch-project/common-utils#256

[derek-ho]

Hi all, I am trying to enable this for a few plugins (observability, sql, dashboards-reports, dashboards-visualizations), and am wondering if it makes sense to disable backward compatibility tests since this is the first release on windows/macos.
Also seeing several errors like the following for windows/macos CI:
Could not HEAD 'https://artifacts.opensearch.org/releases/core/opensearch/1.1.0/opensearch-min-1.1.0-windows-x64.zip'. Received status code 403 from server: Forbidden. Is this a known infra issue/will be resolved at some point? Thanks

[peterzhuamazon]

Hi all, I am trying to enable this for a few plugins (observability, sql, dashboards-reports, dashboards-visualizations), and am wondering if it makes sense to disable backward compatibility tests since this is the first release on windows/macos. Also seeing several errors like the following for windows/macos CI: Could not HEAD 'https://artifacts.opensearch.org/releases/core/opensearch/1.1.0/opensearch-min-1.1.0-windows-x64.zip'. Received status code 403 from server: Forbidden. Is this a known infra issue/will be resolved at some point? Thanks

There is no 1.1.0 windows for sure because we havent release windows yet......
@CEHENKLE @bbarani wonder if we want to enable this once we have 1.x windows release later?

Thanks.

[dblock]

I think we should manually publish an 2.3.0 Windows build that I know we were able to produce, to support bcw. If we ship 2.4.0 with Windows support and 2.5.0 fails to upgrade because of something in 2.4.0 it will be a lot more difficult to fix.

[bbarani]

@peterzhuamazon Can we publish the Windows -min artifacts to artifacts.opensearch.org as well to unblock opensearch-project/sql#928?

[peterzhuamazon]

We already have 2.4.0 min in snapshots on artifacts, not 2.3.0 tho.

[peterzhuamazon]

My point being that are pointing to the wrong location, should be snapshots not releases or release-candidates anymore.

[dblock]

We found that a number of child issues were closed with only partial working CI (unit tests, but not integration tests). Those issues have been reopened and I updated the description here to reflect that we want 100% parity in tests across all supported platforms, linux and windows.