SKU / SKU Price Details-related issues - backlog cleanup

[ijurica]

Description

SKU / SKU Price Details-related tasks identified at the Members meeting on May 24, 2024:

1. SKU categorization: Identify and specify a list (hierarchy) of SKU categorization attributes, if possible both normalized and provider-specific, applicable across all providers and SKUs. (see issue SKU categorization columns #315 )

2. SKU Details: Identify and specify the most prominent SKU details, i.e., attributes - if possible, these attributes should be relevant to a larger number of SKUs, with values that are provider and SKU specific.

3. SKU Price Details: Identify and specify prominent SKU price details, i.e., attributes such as tiered-pricing-related attributes, terms, etc. (Note: SKU Price inherits all attributes from SKU, but some attributes are specific to the price itself). Check if it is possible to mandate that all providers specify these attributes at SKU Price level rather than SKU level.

4. SKU / SKU Price details delivery format: Specify format in which this information will be included in the FOCUS dataset. Consider:

   • Adding SKU Details and SKU Price Details columns (key-value, i.e., simple JSON)
   • Adding a dedicated column for each SKU categorization and each prominent SKU detail and SKU Price detail attribute, while the remaining attributes are contained in the SKU details and SKU Price details columns (key-value, i.e., simple JSON)
   • Adding separate dataset(s) while using SkuId and SkuPriceId for joining the data (note: this option wasn't very popular at the meeting)

More details and useful information available in SKU Details Delivery Options and Brainstorming space (FOCUS)

Note: Considering SkuId and SkuPriceId can already be used to fetch SKU/SKU Price Details using existing Provider Pricing APIs, we might recommend that providers include these attributes in their APIs as well.

Github issue or Reference

Other existing Github issues related to SKU / SKU Price Details:

• [Proposal] Add support for describing different types of usage of a single product. #339
• SkuCapacity / SkuCapacityUnit #320
• SKU description #316
• SKU categorization columns #315
• [Work_Item] Clarify definition of SKU ID #314
• Provider SKU size  #313
• [Proposal] SKU tier #312
• [Proposal] Handle when SKU region is different from resource region #303
• SKU term #153
• [Proposal] Create Source, Destination, and LocationType Dimensions for all Data Transfer Costs #73

[jpradocueva]

Action Items:

• TS2-#473: Michael to ensure all items in the current issue list are covered by existing or new issues.
• TS2-#473: Assign specific SKU-related tasks to Task Force 3 for detailed review and action.

[jpradocueva]

Summary Members' call on Oct 17:

Primary Issue: Several issues related to SKU and SKUPrice details have accumulated in the backlog, and this item is intended to consolidate them and determine how best to proceed.
Core Problem: The backlog contains multiple SKU-related issues that may overlap or duplicate one another, complicating the scoping process for version 1.2. The group needs to determine which items are still relevant and how to prioritize them.
Divergent Views: Some members suggested that many of the older SKU issues should be closed to streamline the backlog. Others argued that some of the issues, while old, may still be relevant and should be included in 1.2.
Final Agreement: The group agreed to keep the issue open for now, with a plan to review and group similar SKU issues. Items relevant to version 1.2 will be identified, and older or redundant items will be closed.
Action Items:

• [Members-#473] Irena, @ijurica : Review the list of SKU/SKUPrice-related issues to determine which should be considered for 1.2.

[shawnalpay]

Discussed in Oct 22 TF1 call. Decided that only:

SKU Details: Identify and specify the most prominent SKU details, i.e., attributes - if possible, these attributes should be relevant to a larger number of SKUs, with values that are provider and SKU specific.

Needs a Work Item that will represent the several issues that are in the backlog representing SKU Details.

Also create a placeholder Work Item for:

SKU / SKU Price details delivery format: Specify format in which this information will be included in the FOCUS dataset.

[shawnalpay]

@ijurica Now that you have created #619, can we close this issue, or are there any other deliverables for which we need issues?

[ijurica]

@shawnalpay, considering that I've mentioned them in the Issue #619, I suggest we close the following [SKU, SKU Price] Related Issues as well:

• SkuCapacity / SkuCapacityUnit #320
• [Proposal] Create Source, Destination, and LocationType Dimensions for all Data Transfer Costs #73
• SKU description #316

---

Considerations:

• Incorporate requirements from the Closed [SKU, SKU Price] Properties-Related Issues Consolidation List (list of issues superseded by this work item)
  ...

Closed [SKU, SKU Price] Properties-Related Issues Consolidation List
List of issues superseded by this work item:

• SKU Properties & Providers alignment #495
• SkuCapacity / SkuCapacityUnit #320
• Provider SKU size  #313
• [Proposal] SKU tier #312
• [Proposal] Create Source, Destination, and LocationType Dimensions for all Data Transfer Costs #73
• [Proposal] Handle when SKU region is different from resource region #303
• SKU term #153
• SKU description #316
  ...

[jpradocueva]

Comments from Members' call on Oct 31:

Analysis: Superseded by other work items covering SKU price details, which makes this issue redundant.
Agreements: Shawn will close #473 and any directly related issues that are now superseded.