Skip to content

Conversation

@viniciusdc
Copy link
Contributor

@viniciusdc viniciusdc commented Jun 27, 2025

Reference Issues or PRs

closes #3087

What does this implement/fix?

Put a x in the boxes that apply

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds a feature)
  • Breaking change (fix or feature that would cause existing features not to work as expected)
  • Documentation Update
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Build related changes
  • Other (please describe):

Documentation

  • For new features or enhancements, a corresponding PR has been opened in the documentation repository (if applicable)
    • Link to docs PR:

Testing

  • Did you test the pull request locally?
  • Did you add new tests?

How to test this PR?

  • Deploy a nebari cluster from this branch
  • From within a jupyterlab instance running for a test user with appropriate dask access (give developer to the user under keycloak)
  • Deploy e dask-gateway cluster, and under the profiles attest that the default profiles for the worker matches the one specifed in the yaml

Any other comments?

@viniciusdc viniciusdc requested a review from a team as a code owner June 27, 2025 19:23
@viniciusdc viniciusdc requested review from dcmcand and marcelovilla and removed request for a team June 27, 2025 19:23
@viniciusdc viniciusdc changed the title allow passing default attr to dask worker profiles [ENH] allow passing default attr to dask worker profiles Jun 27, 2025
@viniciusdc viniciusdc added this to the 2025.7.1 milestone Jul 23, 2025
@viniciusdc viniciusdc removed this from the 2025.10.1 milestone Oct 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: New 🚦

Development

Successfully merging this pull request may close these issues.

[ENH] - Allow passing default options to dask worker profiles

2 participants