Include provider in OCP/cloud tag sql params

[lcouzens]

Jira Ticket

COST-####

Description

This change will add source_uuid to reporting_ocp{cloud}tags_summary.sql in order to reduce the select scale set. The more clusters/providers a customer has the slower this query is going to become.

Additionally fixed up some logging.

Testing

1. Checkout Branch
2. Restart Koku
3. Hit endpoint or launch shell
   1. You should see ...
4. Do more things...

Release Notes

• proposed release note

* [COST-####](https://issues.redhat.com/browse/COST-####) Fix some things

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.1%. Comparing base (01d3b3e) to head (72af472).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #5261     +/-   ##
=======================================
- Coverage   94.1%   94.1%   -0.0%     
=======================================
  Files        375     375             
  Lines      31429   31429             
  Branches    4627    4627             
=======================================
- Hits       29573   29571      -2     
- Misses      1185    1187      +2     
  Partials     671     671             

[myersCody]

For each ocp on cloud row, there are two bill ids associated with it.

1. report_period_id (The OCP bill id)
2. cost_entry_bill_id (The AWS bill id)

The question I have is why are we not filtering by the report_period_id within the tag summary sql?

We could pass in the current_report_period_id to the tag_information call, because the line right before it utilizes it.

Also, I am not sure if the title of this issue correctly describes all the changes being made in the PR. We are changing the tag sql params for all ocp on cloud providers.

[lcouzens]

For each ocp on cloud row, there are two bill ids associated with it.

1. report_period_id (The OCP bill id)

2. cost_entry_bill_id (The AWS bill id)

The question I have is why are we not filtering by the report_period_id within the tag summary sql?

We could pass in the current_report_period_id to the tag_information call, because the line right before it utilizes it.

Also, I am not sure if the title of this issue correctly describes all the changes being made in the PR. We are changing the tag sql params for all ocp on cloud providers.

Thats a reasonable suggestion that probably reduces the dataset down even more than just by cluster. 😄 Long as this SQL still works as expected with the smaller dataset I'm fine with that approach. I'll push that change up and we can give it a whirl. Thanks Cody!

[lcouzens]

/retest