-
Notifications
You must be signed in to change notification settings - Fork 154
acc: parameterize bundle name in job_permissions test to avoid stale deploy locks #4772
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
2 changes: 1 addition & 1 deletion
2
...undle/apps/job_permissions/databricks.yml → .../apps/job_permissions/databricks.yml.tmpl
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| bundle: | ||
| name: test-bundle | ||
| name: $UNIQUE_NAME | ||
|
|
||
| permissions: | ||
| - level: CAN_MANAGE | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Suggestion] App name
my-appis still hardcodedThe bundle name is now parameterized (fixing deploy locks), but the app resource name
my-app(line 24) remains hardcoded. If a prior run fails after creating the app but beforebundle destroy, the next run could hitRESOURCE_ALREADY_EXISTS. The sibling tests (compute_size,git_source) already parameterize the app name asapp-$UNIQUE_NAMEand include cleanup traps.This is orthogonal to the PR's stated goal (deploy locks are fixed correctly), but worth addressing as a follow-up for consistency with sibling tests.
Suggestion: Consider parameterizing the app name and adding a
trap cleanup EXIThandler as a follow-up.