[DABs]: Prefix is a huge win for when deploying resources but ideally on a case by case there is a configuration for each resource that allows for this prefix to not be added

Open
#5,780 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
cli

Research direction

Start by tracing how DABs applies the target prefix to catalogs, jobs, and schemas. Review the existing resource configuration and deployment tests, then define and verify a per-resource opt-out while preserving current prefix behavior for resources without the option.

Written by the indexing model from the issue text.

Description

DABs Enhancement Stale

A great example here is if I have a prod target with a prefix that is "prod"
I would want this to apply to my catalogs and jobs and all of that but not to my schemas.
Ideally there is a way to turn this off with a genera resource configuration option so that prefix is not applied to that resource in question or maybe even a top level config that just allows me to specify not to apply prefixes to a given resource,
This would still allow for it to be backwards compatible but give a better feature set.

Dominant language
Go
Stars
427
Forks
267
Avg merge
2d 1h
Merged PRs (30d)
233

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/cli

All issues in databricks/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.