RHINENG-15237: Update floorist queries and payload file to randomly add different ca…

[thearifismail]

…nonical_facts

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED

Overview

This PR is being created to address RHINENG-15237.
It also updates the utils/payloads.py file, to generate news hosts by randomly choosing to add provider_id, subscription_manager_id, or bios_uuid. insights_id is always used. Randomization also picks a reporter among ["cloud-connector", "puptoo", "rhsm-conduit", "rhsm-system-profile-bridge", "yuptoo"].

The Floorist queries will be put the results in AWS S3 buckets which will be used for creating metrics.

PR Checklist

• Keep PR title short, ideally under 72 characters
• Descriptive comments provided in complex code blocks
• Include raw query examples in the PR description, if adding/modifying SQL query
• Tests: validate optimal/expected output
• Tests: validate exceptions and failure scenarios
• Tests: edge cases
• Recovers or fails gracefully during potential resource outages (e.g. DB, Kafka)
• Uses type hinting, if convenient
• Documentation, if this PR changes the way other services interact with host inventory
• Links to related PRs

Secure Coding Practices Documentation Reference

You can find documentation on this checklist here.

Secure Coding Checklist

• Input Validation
• Output Encoding
• Authentication and Password Management
• Session Management
• Access Control
• Cryptographic Practices
• Error Handling and Logging
• Data Protection
• Communication Security
• System Configuration
• Database Security
• File Management
• Memory Management
• General Coding Practices

[strider]

LGTM

[kruai]

@thearifismail I'm OK with these changes, but it feels like they should be 2 separate PRs. Are the changes to the payload file related at all to the Jira this PR is addressing?

[thearifismail]

@thearifismail I'm OK with these changes, but it feels like they should be 2 separate PRs. Are the changes to the payload file related at all to the Jira this PR is addressing?

I did think about creating two separate PRs because apparently they are. Since testing floorist queries needed variety in hosts canonical_facts and reporters, I submitted the changes in one PR.

[kruai]

@thearifismail I'm OK with these changes, but it feels like they should be 2 separate PRs. Are the changes to the payload file related at all to the Jira this PR is addressing?

I did think about creating two separate PRs because apparently they are. Since testing floorist queries needed variety in hosts canonical_facts and reporters, I submitted the changes in one PR.

I wasn't aware that payloads.py was being used to test Floorist queries; if that's the case, this seems reasonable enough to me.

[kruai]

LGTM, but please do not merge this until we're told it's safe to merge PRs again (see this slack thread)