While removing a segment of inactive code within our AWS processing pathway, I discovered that we omit the invocation of the reporting_awsenabledtagkeys.sql file specific to AWS. Presently, our reliance rests solely on the final post-processing step to populate the AWS enabled tag keys model.

• https://github.com/search?q=repo%3Aproject-koku%2Fkoku+post_processor+finalize_post_processing&type=code

It might be prudent to reconsider the necessity of the populate_enable_tag_keys function for our other cloud providers. There is a possibility that it represents redundant code that we could potentially eliminate from our codebase.

• https://github.com/search?q=repo%3Aproject-koku%2Fkoku%20populate_enabled_tag_keys&type=code