Skip to content

Conversation

@shreyas-goenka
Copy link
Contributor

@shreyas-goenka shreyas-goenka commented Jun 12, 2025

Why

This PR mirrors the validation we added for required fields not being set: #3044

Tests

A new acceptance test.

@eng-dev-ecosystem-bot
Copy link
Collaborator

eng-dev-ecosystem-bot commented Jul 25, 2025

Run: 16831523227

Env ✅‌pass 🔄‌flaky 🙈‌skip
✅‌ aws linux 309 466
✅‌ aws windows 310 465
✅‌ aws-ucws linux 415 366
✅‌ aws-ucws windows 416 365
🔄‌ azure linux 304 5 465
🔄‌ azure windows 309 1 464
✅‌ azure-ucws linux 417 363
✅‌ azure-ucws windows 418 362
✅‌ gcp linux 308 467
✅‌ gcp windows 309 466
6 failing tests:
Test Name azure linux azure windows
TestAccept/bundle/deployment/bind/dashboard/recreation 🔄‌flaky ✅‌pass
TestAccept/bundle/templates/default-python/combinations/classic 🔄‌flaky ✅‌pass
TestAccept/bundle/templates/default-python/combinations/classic/DATABRICKS_CLI_DEPLOYMENT=terraform/DLT=yes/NBOOK=no/PY=yes 🔄‌flaky ✅‌pass
TestAccept/bundle/templates/default-python/integration_classic 🔄‌flaky ✅‌pass
TestAccept/bundle/templates/default-python/integration_classic/DATABRICKS_CLI_DEPLOYMENT=terraform/UV_PYTHON=3.13 🔄‌flaky ✅‌pass
TestSyncEnsureRemotePathIsUsableIfRepoExists ✅‌pass 🔄‌flaky

@shreyas-goenka shreyas-goenka changed the title Validate enum bundle fields Validate values for enum fields in DABs Jul 25, 2025
@shreyas-goenka shreyas-goenka changed the title Validate values for enum fields in DABs Add warning when invalid value is specified for enum field Jul 25, 2025
@shreyas-goenka shreyas-goenka changed the title Add warning when invalid value is specified for enum field Add warning when an invalid value is specified for enum field Jul 25, 2025

// Check if the value is in the list of valid enum values
validValue := false
for _, valid := range validValues {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is not efficient, and should ideally be a set or a map. But given that these lists only have 1-10 elements, the CPU time here will not make a difference in practice at all.

@shreyas-goenka shreyas-goenka marked this pull request as ready for review July 25, 2025 15:34
@shreyas-goenka shreyas-goenka added this pull request to the merge queue Aug 8, 2025
Merged via the queue into main with commit d13598f Aug 8, 2025
13 checks passed
@shreyas-goenka shreyas-goenka deleted the validate-enum-v1 branch August 8, 2025 14:02
deco-sdk-tagging bot added a commit that referenced this pull request Aug 13, 2025
## Release v0.264.0

### Dependency updates
* Upgrade TF provider to 1.86.0 ([#3374](#3374))
* Update Go SDK to 0.79.0 ([#3376](#3376))

### CLI
* Fixed panic when providing a CLI command with an incorrect JSON input ([#3398](#3398))

### Bundles
* Changed logic for resolving `${resources...}` references. Previously this would be done by terraform at deploy time. Now if it references a field that is present in the config, it will be done by DABs during bundle loading ([#3370](#3370))
* Add support for tagging pipelines ([#3086](#3086))
* Add warning for when an invalid value is specified for an enum field ([#3050](#3050))
* Add support for running specified job tasks instead of all job tasks ([#3388](#3388))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants