[terraform-ibm-observability-da] Add estimated-usage.yml to improve the calculated cost estimation

[ocofaigh]

We need to make a cost estimation change for the SCC and Observability DA’s. Both DAs thinks the estimated COS storage usage is 1TB, and that sounds grossly underestimated. We need to put in a yaml file like this : https://github.com/terraform-ibm-modules/terraform-ibm-watsonx-saas-da/blob/main/estimated-usage.yml

[tyao117]

got a sample yaml to use :

# You can use this file to define resource usage estimates for Infracost to use when calculating
# the cost of usage-based resource, such as AWS S3 or Lambda.
# `infracost breakdown --usage-file infracost-usage.yml [other flags]`
# See https://infracost.io/usage-file/ for docs
version: 0.1
# resource_type_default_usage:
  ##
  ## The following usage values apply to each resource of the given type, which is useful when you want to define defaults.
  ## All values are commented-out, you can uncomment resource types and customize as needed.
  ##
  # ibm_cos_bucket:
    # accelerated_archive_capacity: 0.0
    # accelerated_archive_restore: 0.0
    # archive_capacity: 0.0
    # archive_restore: 0.0
    # aspera_egress: 0.0
    # aspera_ingress: 0.0
    # class_a_request_count: 0
    # class_b_request_count: 0
    # monthly_average_capacity: 0.0
    # monthly_data_retrieval: 0
    # public_standard_egress: 0.0
  # ibm_resource_instance:
    # appconnect_gigabyte_transmitted_outbounds: 0.0
    # appconnect_thousand_runs: 0.0
    # appconnect_vcpu_hours: 0.0
    # appid_advanced_authentications: 0
    # appid_authentications: 0
    # appid_users: 0
    # kms_key_versions: 0
    # secretsmanager_active_secrets: 0
    # secretsmanager_instance: 0
    # logdna_gigabyte_months: 0.0
    # activitytracker_gigabyte_months: 0.0
    # sysdig-monitor_NODE_HOURS: 0.0
    # sysdig-monitor_CONTAINER_HOURS: 0.0
    # sysdig-monitor_API_CALL_HOURS: 0.0
    # sysdig-monitor_TIME_SERIES_HOURS: 0.0
    # continuousdelivery_authorized_users: 0
    # wml_capacity_unit_hour: 0.0
    # wml_instance: 0.0
    # wml_class1_ru: 0.0
    # wml_class2_ru: 0.0
    # wml_class3_ru: 0.0
    # wa_instance: 0.0
    # wa_monthly_active_users: 0.0
    # wa_monthly_voice_users: 0.0
    # wd_instance: 0.0
    # wd_documents: 0.0
    # wd_queries: 0.0
    # wd_custom_models: 0.0
    # wd_collections: 0.0
    # scc_evaluations: 0.0
    # data-science-experience_CAPACITY_UNIT_HOURS: 1.0
    # sysdig-secure_MULTI_CLOUD_CSPM_COMPUTE_INSTANCES: 0.0
    # sysdig-secure_NODE_HOURS: 0.0
    # sysdig-secure_VM_NODE_HOUR: 0.0
    # aiopenscale_RESOURCE_UNITS: 1.0
    # aiopenscale_MODELS_PER_MONTH: 1.0
resource_usage:
  ##
  ## The following usage values apply to individual resources and override any value defined in the resource_type_default_usage section.
  ## All values are commented-out, you can uncomment resources and customize as needed.
  ##
  module.cos[0].module.buckets.module.buckets["base-security-services-bucket"].ibm_cos_bucket.cos_bucket[0]:
    archive_capacity: 0.0 # Amount of your estimated archive storage in GB
    archive_restore: 0.0 # Amount of data restored from its archived state in GB
    accelerated_archive_capacity: 0.0 # Amount of your estimated archive storage in GB
    accelerated_archive_restore: 0.0 # Amount of data restored from its archived state in GB
    aspera_ingress: 0.0 # Amount of data uploaded with Aspera in GB
    aspera_egress: 0.0 # Amount of data downloaded with Aspera in GB
    class_a_request_count: 0 # Monthly number of Class A requests, 1k
    class_b_request_count: 0 # Monthly number of Class B requests 10k
    monthly_average_capacity: 10 # Average amount of data stored in GB
    monthly_data_retrieval: 0 # Amount of data retrieved in GB
    public_standard_egress: 0.0 # Amount of data downloaded in GB
  module.scc.ibm_resource_instance.scc_instance:
    scc_evaluations: 1
  module.scc_wp[0].ibm_resource_instance.scc_wp:
    sysdig-secure_MULTI_CLOUD_CSPM_COMPUTE_INSTANCES: 1
    sysdig-secure_NODE_HOURS: 1
    sysdig-secure_VM_NODE_HOUR: 1

[maheshwarishikha]

@tyao117 Any specific reason that we use the cost of usage-based resource, such as AWS S3 or Lambda. in comments? Or can we modify it for IBM resources?

[terraform-ibm-modules-ops]

:tada: This issue has been resolved in version 1.7.0 :tada:

The release is available on:

• GitHub release
• v1.7.0

Your semantic-release bot :package::rocket: