[Feature Request] Support updating additionalArguments with aws:configurePackage
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 357
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I am using Distributor and aws:configurePackage and I want to update my association `additionalArguments`.
The problem is that if the association only changes the `additionalArguments` the installation will be skipped with a message like:
```
$PACKAGE_ARN $VERSION is already installed
```
First I was forcing the package to `Uninstall` then `Install` to apply the changes, but it is a bit cumbersome to do from my Terraform code.
I figured out that you can use the undocumented `validate` step, so I added a custom `validate.sh` to the package zip file to check if arguments have drifted. This approach worked because the installationCheck will fail and force a reinstall but this feels hacky.
Am I missing something?
It would be nice to have a way to handle this case properly.
Contributor guide
Research direction
Start by tracing aws:configurePackage, especially the installationCheck and validate steps described in the issue, and review how Distributor handles association additionalArguments. Done means changing only additionalArguments causes the package state to update without forcing Uninstall/Install or relying on a custom validate.sh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100