-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use environment variable for passing the private key password #2094
Conversation
…y password and env var for kubernetes
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2094 +/- ##
=======================================
Coverage 94.14% 94.14%
=======================================
Files 255 255
Lines 15789 15783 -6
=======================================
- Hits 14864 14859 -5
+ Misses 925 924 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
if self.deplopyment_type == DOCKER_COMPOSE_DEPLOYMENT: | ||
agent_vars[ENV_VAR_AEA_PASSWORD] = "$OPEN_AUTONOMY_PRIVATE_KEY_PASSWORD" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will store the value of AEA_PASSWORD
as $OPEN_AUTONOMY_PRIVATE_KEY_PASSWORD
in the docker-compose.yaml
so the user can pass the password as OPEN_AUTONOMY_PRIVATE_KEY_PASSWORD
when running the deployment
agent_vars[ENV_VAR_AEA_PASSWORD] = os.environ.get( | ||
"OPEN_AUTONOMY_PRIVATE_KEY_PASSWORD", "" | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately the kubernetes does not provide such functionalities so we'll have to store them the old way
Proposed changes
--password
flagOPEN_AUTONOMY_PRIVATE_KEY_PASSWORD
as environment variable for passing private key passwordFixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an
x
in the box that appliesChecklist
Put an
x
in the boxes that apply.main
branch (left side). Also you should start your branch off ourmain
.