feat(ec2): add support for environment files and variables in systemd#29629
feat(ec2): add support for environment files and variables in systemd#29629mergify[bot] merged 11 commits intoaws:mainfrom
Conversation
aws-cdk-automation
left a comment
There was a problem hiding this comment.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.
|
Exemption Request No README updates needed since this added optional features that goes beyond basic systemd service creation |
There was a problem hiding this comment.
Thanks for contributing 👍
Left some comments for minor adjustments.
Also, you could add some documentation in Configuring Instances using CloudFormation Init (cfn-init).
packages/@aws-cdk-testing/framework-integ/test/aws-ec2/test/integ.instance-init.ts
Show resolved
Hide resolved
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
lpizzinidev
left a comment
There was a problem hiding this comment.
Thanks 👍 Added a suggestion to change the wording for the documentation
Co-authored-by: Luca Pizzini <lpizzini7@gmail.com>
|
@lpizzinidev what do I do from here? Never got a PR this far in this repo. Do I just wait for it to be merged? |
|
Hey @razin99 ✋ |
TheRealAmazonKendra
left a comment
There was a problem hiding this comment.
Thank you for your work on this. I'm thinking that it's likely that this change is good to go with one clarifying question: can a user provide both environmentVariables and environmentFiles or is it an either/or situation?
If they can provide both, this looks ready.
They can provide both, as this is a supported behaviour by systemd. From what I've read (here), anything Quote from documentation:
|
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one. |
Reason for this change
Allow users to define
EnvironmentandEnvironmentFilein a systemd service file.Description of changes
Added 2 new properties for
ec2.InitService.systemdConfigFile:environmentVariableswhich is a string key value pairenvironmentFileswhich is a list of file pathsDescription of how you validated changes
I have added a unit test.
Documentations referred to:
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license