Customize the prefix assigned to resources deployed in development mode

[domcorvasce]

Changes

Note: I went with this approach so everyone can fit it to their needs but IMO it would be enough to just change the process_target_mode module so the prefix matches the target name instead of being hard coded as dev. I’d gladly rework the PR if this simpler approach is enough.

All the names of the resources (i.e. jobs, pipelines, models endpoints) deployed in development mode are prefixed with [dev user_name] which can be confusing when an organization has multiple development environments to choose from.

This pull request adds an optional resource_name_prefix field to the bundles target object, allowing developers to specify custom prefixes:

bundle
  name: test

targets:
  dev:
    # Deployed resources get prefixed with '[hello test]'
    resource_name_prefix: hello ${bundle.name}
    mode: development

Open points

• Is this something you would be open to accept?
• This is the first time I contribute to the project so I could have missed something
• I agree the name of the field might be a bit confusing: I'm open to suggestions

Tests

• Added a new unit test to the process_target_mode module test suite

[lennartkats-db]

Thanks @domcorvasce for this contribution. It would be great to have a feature like this! We had the request to make these transformations more customizable from multiple customers. We'd like to do so for the prefix and for other things like the tags that are automatically asserted.

I'll discuss with the team what the right name is for a prefixing property, and if it should perhaps be nested under a property like transform:. And I'll need to check in with legal about a contributor's license agreement. Please bear with us as it may take a bit of time to complete both of these things during the holidays.