The generic-client-tests CI does not pick up changes from monorepo

[trivikr]

Describe the bug

The generic-client-tests CI does not pick up changes from monorepo

• Workflow failure when package client-documentation-generator was renamed to service-client-documentation-generator https://github.com/aws/aws-sdk-js-v3/runs/3957113601?check_suite_focus=true
• Workflow failure when NODE_USE_FIPS_ENDPOINT_CONFIG_OPTIONS was added in config-resolver https://github.com/aws/aws-sdk-js-v3/runs/4016491875

Your environment

SDK version number

main

Is the issue in the browser/Node.js/ReactNative?

N/A

Details of the browser/Node.js/ReactNative version

N/A

Steps to reproduce

Export new code from utility packages, and import it from clients.
Example PR: #2937

Observed behavior

The generic-client-tests CI fails.

Expected behavior

The generic-client-tests test CI should not fail.

Additional context

Temporary fixes to build impacted packages in CI:

• service-client-documentation-generator test: unblock generic client test #2922
• config-resolver 875962a (#2937)

[trivikr]

One solution would be to create a private generic client, just like protocol_tests.
May be create a new workspace generic_client and copy aws-echo-service to it?

[AllanZhengYP]

/cc @adamthom-amzn Can we move the aws-echo-service client to the workspace just like other protocol test clients?

[trivikr]

Decision:

• We will protocol tests and generic client in one folder (say private)
• We will prefix something else for protocol tests in addition to aws-, say (aws-procotol-test-). This way, we know which workspaces in private are protocol tests.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.