During deploy, if certificate was changed in dashmate config, instead of updating SSM we rewrite config back to old value from SSM. It prevents dashmate helper to update certificates automatically.
What was done?
Write ID from SSM to config only if the value in config is null. We do not overwrite new certificate, created with the dashmate helper or the obtain command.
Update SSM when ID from config and SSM are different. It means certificate was updated with the dashmate helper or the obtain command.
How Has This Been Tested?
None
Breaking Changes
None
Checklist:
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation
For repository code-owners and collaborators only
[x] I have assigned this pull request to a milestone
Issue being fixed or feature implemented
During deploy, if certificate was changed in dashmate config, instead of updating SSM we rewrite config back to old value from SSM. It prevents dashmate helper to update certificates automatically.
What was done?
How Has This Been Tested?
None
Breaking Changes
None
Checklist:
For repository code-owners and collaborators only