Skip to content

Add kaggle kernels push flags for attaching secrets and passing runtime parameters#944

Closed
huyhoang171106 wants to merge 1 commit intoKaggle:mainfrom
huyhoang171106:feat/add-kaggle-kernels-push-flags-for-attach
Closed

Add kaggle kernels push flags for attaching secrets and passing runtime parameters#944
huyhoang171106 wants to merge 1 commit intoKaggle:mainfrom
huyhoang171106:feat/add-kaggle-kernels-push-flags-for-attach

Conversation

@huyhoang171106
Copy link
Copy Markdown

Summary

Extend the kernels push command parser to accept user-provided secret names (not values) and input variables at push time. This addresses the issue request while preserving security constraints raised in the thread. The CLI should support attaching existing account-level secrets to the notebook version being pushed, and passing explicit non-secret key/value parameters.

Files changed

  • src/kaggle/cli.py (modified)

Testing

  • Not run in this environment.

Closes #582

…nd passing runtime parameters

Signed-off-by: Nguyen Huy Hoang <181364121+huyhoang171106@users.noreply.github.com>
@google-cla
Copy link
Copy Markdown

google-cla bot commented Mar 26, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@huyhoang171106
Copy link
Copy Markdown
Author

Auto-closed: CI checks failed

The following checks failed: cla/google

Closing this PR since required CI checks did not pass. Sorry for the inconvenience.

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.

Can we add parameters/secrets while pushing the kernels ?

1 participant