Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

Add custom environment variable options to pool configuration #253

Merged
merged 4 commits into from
Jan 15, 2019

Conversation

jackpimbert
Copy link
Contributor

Add the option to include custom environment variables in the pool configuration, see #252 for more information.

Pull Request Checklist

  • Review the contributing guidelines
  • Outstanding issue linked, if applicable
  • PR should only be opened against master if it includes no features (open against develop otherwise)
  • Commit messages should conform to good style practices
  • PR should pass all checks and have no conflicts

Description

This is a possible start on how to solve #252, however this may be the wrong approach. Any feedback is welcome.

- Add the option to include custom environment variables in the pool
  configuration
- This allows users to setup Batch environment variables for the start
  task
- This in turn could allow for the ability to use batch insights
@msftclas
Copy link

msftclas commented Dec 20, 2018

CLA assistant check
All CLA requirements met.

@alfpark
Copy link
Collaborator

alfpark commented Jan 10, 2019

Apologies for the delay, can you add the env var spec to the pool schema for validation?

- CHANGELOG updated with pool env var feature
@jackpimbert
Copy link
Contributor Author

Done - please let me know if you think anything else is required. Will a develop-cli docker image be built with the latest changes if they are merged in? Or will there be another release soon?

@alfpark
Copy link
Collaborator

alfpark commented Jan 11, 2019

develop-cli should auto build after commit, but it looks like it's not triggering for some reason on the latest pushes. I'll have to investigate.

- Added a keyvault option to the pool configuration
- Updated docs, schemas and templates accordingly
- Changed schema type from `str` to `text` for env vars
- Add a keyvault client check to ensure a valid client is used when
  using keyvault to add env vars to the start task.
@jackpimbert
Copy link
Contributor Author

I've made the (possibly final) minor change for this PR and have tested the changes manually to ensure that they do enable the use of batch insights, as specified in #252.

Thanks for the support, and i'll keep an eye on the progress of the next iteration of this issue as discussed in the earlier comments.

@alfpark alfpark merged commit fd21b8e into Azure:develop Jan 15, 2019
alfpark pushed a commit that referenced this pull request Jan 16, 2019
* Add env vars option to pool configuration

- Add the option to include custom environment variables in the pool
  configuration
- This allows users to setup Batch environment variables for the start
  task
- This in turn could allow for the ability to use batch insights

* Add env var spec to pool schema for validation

- CHANGELOG updated with pool env var feature

* Add a keyvault option for pool env vars

- Added a keyvault option to the pool configuration
- Updated docs, schemas and templates accordingly
- Changed schema type from `str` to `text` for env vars

* Add keyvault client check

- Add a keyvault client check to ensure a valid client is used when
  using keyvault to add env vars to the start task.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants