As we all know, the main method of cost attribution for serverless compute is with budget (sometimes called usage) policies (Public Preview). This is a new paradigm compared with the tagging of both classic compute and serverless SQL warehouses.
The Jobs UI further makes the clarification we should not confuse tags for organising with cost tags. ("Tags are key-value pairs that you can use to organize your jobs.")
However, I have found three things in Databricks that don't make sense based on this.
1. For jobs created with asset bundles and its `tags` parameter, the organisation tags actually appear in the cost break down usage dashboard. Isn't this a bug? How does this interact with potential budget_policy_id tags? When I tried this a couple of months ago, the tags did not appear until I made them a part of a budget policy.
2. It does not appear to be possible in the UI to set a budget policy for certain serverless job types. For most serverless types, the usage policy show up in the settings menu above tags and below Environment/Compute. However it doesn't even show up as blank for serverless jobs created with asset bundle, ClickOps jobs that simply wrap Salesforce managed ingestion or Terraform jobs that wrap declarative pipelines. I am not sure what the rule is here.
3. The tag UI element in the budget policy seems broken as show blank even it the tags are set properly.
Are you scraping budget policy or how should we think about cost tagging serverless processes going forward?
