Unify File Formats across AWS, Azure, GCP

[vpritamani-rubrik]

Unify data formats for all workloads in each script as detailed:

In all CSV files the field order should be:

• Account ID
• Account Alias
• Region
• Parent Object ID and Parent Object Name (if Needed)
  o For multiple parents, pair ID and name columns next
  to each other with ID first and Name second
• Object ID (if applicable)
• Object Name (tag)
• Quantity of sub object (ie. disks) (if applicable)
• InBackupPlan column (True/False)
• BackupPlan Name- Size B
• Object capacity(ies)
  o The capacity header should begin with ""Provisioned"" or ""Used""
  depending on if the capacity is based on a Provisioned or
  used/actual number. If another description such as quota is
  is required, use that instead.
  o If an object has multiple capacities and then a total capacity,
  list the total capacity(ies) first
  o If an object has multiple capacities but only some are supported,
  list the supported capacities first.
  o If an object has multiple capacities and some are a faster/more
  expensive tier of capacity list the capacities from faster/more
  expensive to slower/less expensive.
  o Object capacities should be listed in increasing storage units as such:
  * Size KB
  * Size MB
  * Size GB
  * Size TB
• Any object specific fields other than tags
  o Follow other sample files for order like Image Type/Size,
  #CPUs, etc...
• Tags (Multiple columns)

The above is for AWS; for Azure, this would be:

"In all CSV files the field order should be:

• Tenant ID
• Tenant Name
• Subscription ID
• Subscription Name
• Resource Group Name
• Region
• Parent Object ID and Parent Object Name (if Needed)
  o For multiple parents, pair ID and name columns next
  to each other with ID first and Name second
• Object ID (if applicable)
• Object Name (tag)
• InBackupPlan column (True/False)
• BackupPlan Name
• Quantity of sub object (ie. disks) (if applicable)
• Object capacity(ies)
  o The capacity header should begin with ""Provisioned"" or ""Used""
  depending on if the capacity is based on a Provisioned or
  used/actual number. If another description such as quota is
  is required, use that instead.
  o If an object has multiple capacities and then a total capacity,
  list the total capacity(ies) first
  o If an object has multiple capacities but only some are supported,
  list the supported capacities first.
  o If an object has multiple capacities and some are a faster/more
  expensive tier of capacity list the capacities from faster/more
  expensive to slower/less expensive.
  o Object capacities should be listed in increasing storage units as such:
  * Size KB
  * Size MB
  * Size GB
  * Size TB
• Any object specific fields other than tags
  o Follow other sample files for order like Image Type/Size,
  #CPUs, etc...
• Tags (Multiple columns)"

And similarly for GCP as well