Add multi profile testdata for validate and gather application commands

[parikshithb]

Problem

The existing testdata fixtures for validate application and gather application only include profiles that belong to the application. This doesn't test the filtering behavior introduced in the S3 profile fix #503 which we can't tell from the test results.

Proposed solution

Add extra S3 profiles to the hub configmap in the testdata fixtures (profiles not referenced by the VRG). Verify that the report's S3 section only shows the application's profiles, not all profiles from the hub configmap.

Testing

• Validate that the report shows only the 2 application profiles when the hub configmap has 3+.
• Ensure gather only downloads S3 data for the application's profiles.

[Dhanalakshmi-D04]

Hi @parikshithb, I'd like to work on this issue if it's still open. I'll add extra S3 profiles to the hub configmap in the testdata fixtures (not referenced by the VRG) and verify that:

The report only shows the 2 application profiles when the hub configmap has 3+
gather only downloads S3 data for the application's profiles

Let me know if this is available to pick up, and if there's any additional context I should be aware of before starting. Thanks!

[nirs]

Hi @parikshithb, I'd like to work on this issue if it's still open. I'll add extra S3 profiles to the hub configmap in the testdata fixtures (not referenced by the VRG) and verify that:

To test this properly we need to check how this configuration looks in a real cluster. We may get the data from DFBUGS-9708 (you may not have access to this bug).

Another way is to configure ramen testing env with additional s3 profiles but @parikshithb reported that he could not do this.

Try to find a less problematic issue to work on.

[Dhanalakshmi-D04]

Okay , Thank you @nirs !!