support cloud cost credentials

[eranelbaz]

We'd like to add support for our cost credentials.
We'd need the following new resources (and data for each resource)

cost_credentials_project_assignment

Exactly the same as cloud_credentials_project_assignment resource and data. The only difference is that we use different APIs:

• Create
• Delete
• Read - Notice the response format is different than this

aws_cost_credentials

Exactly the same as aws_credentials resource and data (which is a deploy credential, not a cost credential). The schema is exactly the same, and the API calls are the same. The only difference is that the type that should be AWS_ASSUMED_ROLE:

• Create should be called with correct type and data in value
• data should filter by type = AWS_ASSUMED_ROLE

azure_cost_credentials

Similar to aws_cost_credentials resource and data. Should use the same APIs, where type is AZURE_CREDENTIALS . For the schema - see docs - value:

• clientId - required
• clientSecret - required and sensitive
• tenantId - required
• subscriptionId - required
  Other than the schema, differences in API calls are as follows:
• Create should be called with correct type and data in value
• data should filter by type = AZURE_CREDENTIALS

google_cost_credentials

Similar to aws_cost_credentials resource and data. Should use the same APIs, where type is GCP_CREDENTIALS. For the schema - see docs - value:

• tableId - required
• secret - required and sensitive
  Other than the schema, differences in API calls are as follows:
• Create should be called with correct type and data in value
• data should filter by type = GCP_CREDENTIALS

[RLRabinowitz]

When implementing, feel free to create common API logic, and read/create/delete logic, where necessary

[samuel-br]

@RLRabinowitz does the update of aws_credentials with access_key and secret_access_key relevant to aws_cost_cred to?

[RLRabinowitz]

@samuel-br No, cost shouldn’t allow access keys, just assume role.