mirror of https://github.com/databricks/cli.git
4226c88e98
## Changes Prompted by the proposed fix for a tagging-related problem in #810, I investigated how tag validation works. This turned out to be quite a bit more complex than anticipated. Tags at the job level (or cluster level) are passed through to the underlying compute infrastructure and as such are tested against cloud-specific validation rules. GCP appears to be the most restrictive. It would be disappointing to always restrict to `\w+`, so this package implements validation and normalization rules for each cloud. It can pick the right cloud to use using a Go SDK configuration. ## Tests Exhaustive unit tests. The regular expressions were pulled by #814. |
||
|---|---|---|
| .. | ||
| auth | ||
| cmdio | ||
| databrickscfg | ||
| env | ||
| errs | ||
| filer | ||
| fileset | ||
| flags | ||
| git | ||
| jsonschema | ||
| locker | ||
| log | ||
| notebook | ||
| process | ||
| set | ||
| sync | ||
| tags | ||
| template | ||
| terraform | ||
| testfile | ||