Make idle culler settings configurable from the nebari-config.yaml

[iameskild]

Reference Issues or PRs

Closes #1283

This PR makes it so users can configure the JupyterLab idle-culler settings directly from their nebari-config.yaml. The pattern that I used to achieve this was with a Terraform templatefile, which is a pattern that I believe we can use to modify other configuration files in the future (this might include the .bashrc and similar files).

I still need to add documentation for this but to change the idle-culler settings, you can add the following to your nebari-config.yaml:

jupyterlab:
  idle_culler:
    server_shutdown_no_activity_timeout: 100
    kernel_cull_connected: true

Any subset of the idle culler settings can be configured like this. By default, the jupyterlab key is not included.

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):

Testing

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

Any other comments?

[viniciusdc]

Thanks, @iameskild I will have a look in a few minutes

[viniciusdc]

LGTM, I will try deploying a local instance to do a quick test.

[viniciusdc]

Working as expected, I tested in a local deployment but this should also work for the cloud providers as well

[iameskild]

Awesome! Thanks @viniciusdc!

For to be sure, I tested these on the GCP as well 👍

[viniciusdc]

Hi @iameskild we both tested and all seams working, I will go ahead and merge this one.