unmarshal manifest for Load Balanced Web Service: unmarshal "variables": cannot unmarshal field to a string or into a map
I think either the string interpolation capability or an update to it broke something. The following, which is considered value YAML, no longer works and results in the error specified in the title:
Unfortunately, this is causing an issue because I need >= 1.29.0 to take in a fix when a env cluster has been deleted and recreated. But I can't because the interpolation was included before that.
environments:
dev:
http:
healthcheck:
timeout: 10s
variables:
STAFF_EMAILS: '["[email protected]"]'
Hello @richardgavel-ordinaryexperts !
Can you update the manifest to have the below config so that it will skip interpolation at variables.
environments:
dev:
http:
healthcheck:
timeout: 10s
variables:
STAFF_EMAILS: |
["[email protected]", "[email protected]"]
I tried using that syntax, not sure I tried that exact value. Tried so many combinations of escaping, single quotes, double quotes, etc.
On Mon, Mar 18, 2024 at 5:59 PM Adithya Kolla @.***> wrote:
Hello @richardgavel-ordinaryexperts https://github.com/richardgavel-ordinaryexperts !
Can you update the manifest to have the below config so that it will skip interpolation at variables.
environments: dev: http: healthcheck: timeout: 10s variables: STAFF_EMAILS: | @.", @."]
— Reply to this email directly, view it on GitHub https://github.com/aws/copilot-cli/issues/5731#issuecomment-2005219130, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3VJMELGIKSSEEBHMIFQ7WTYY5WTJAVCNFSM6AAAAABE4FLZFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBVGIYTSMJTGA . You are receiving this because you were mentioned.Message ID: @.***>
Hello @richardgavel-ordinaryexperts ! The above config is working fine for me. Can you please test this and let us know how it goes.
This issue is stale because it has been open 60 days with no response activity. Remove the stale label, add a comment, or this will be closed in 14 days.
This issue is closed due to inactivity. Feel free to reopen the issue if you have any further questions!