[Feature Request] Add support for Windows for Greengrass Component
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 357
- PR merge metrics
- No merged PRs in 30d
Description
Please add windows support as well for the Greengrass Component.
I guess it is as easy as adding another `Manifests` entry for `windows`
https://github.com/aws/amazon-ssm-agent/blob/mainline/packaging/greengrass/component.json
```json
{
"Platform": {
"os": "windows",
"architecture": "/amd64|x86_64/"
},
"Lifecycle": {
"SetEnv": {
"SSM_REGISTRATION_ROLE": "{configuration:/SSMRegistrationRole}",
"SSM_RESOURCE_TAGS": "{configuration:/SSMResourceTags}",
"SSM_OVERRIDE_EXISTING_REGISTRATION": "{configuration:/SSMOverrideExistingRegistration}"
},
"Install": {
"Script": "{artifacts:decompressedPath}/artifacts/ssm-setup-cli.exe -env greengrass -install",
"RequiresPrivilege": true
},
"Startup": {
"Script": "{artifacts:decompressedPath}/artifacts/ssm-setup-cli.exe -env greengrass -register",
"RequiresPrivilege": true
},
"Shutdown": {
"Script": "{artifacts:decompressedPath}/artifacts/ssm-setup-cli.exe -env greengrass -shutdown",
"RequiresPrivilege": true
}
},
"Artifacts": [
{
"Uri": "",
"Unarchive": "ZIP",
"Permission": {
"Read": "OWNER",
"Execute": "OWNER"
}
}
]
}
```
Contributor guide
Research direction
Start with packaging/greengrass/component.json and compare the existing manifest entries and artifact layout. Verify the Windows platform, lifecycle scripts, permissions, and artifact settings against the Greengrass component requirements; it is done when the component can be packaged and used for a Windows Greengrass installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100