This repository has been archived by the owner on Mar 20, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 121
Add custom environment variable options to pool configuration #253
Merged
Conversation
This file contains 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
- 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
Apologies for the delay, can you add the env var spec to the pool schema for validation? |
- CHANGELOG updated with pool env var feature
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
suggested changes
Jan 11, 2019
|
alfpark
reviewed
Jan 11, 2019
- Added a keyvault option to the pool configuration - Updated docs, schemas and templates accordingly - Changed schema type from `str` to `text` for env vars
alfpark
suggested changes
Jan 14, 2019
- Add a keyvault client check to ensure a valid client is used when using keyvault to add env vars to the start task.
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
approved these changes
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.
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.
Add the option to include custom environment variables in the pool configuration, see #252 for more information.
Pull Request Checklist
master
if it includes no features (open againstdevelop
otherwise)Description
This is a possible start on how to solve #252, however this may be the wrong approach. Any feedback is welcome.