Correct env variable definitions in ecs-frontend.yaml

[jupiter007]

Fixed (#182)

Currently, the ecs-frontend template includes several environment variables:

            - Name: 'NEXT_PUBLIC_BASE_URL'
              Value: !Ref NextPublicBaseUrl
            - Name: 'NEXT_PUBLIC_SERVER_ENDPOINT'
              Value: !Ref NextPublicServerEndpoint
            - Name: 'NEXT_PUBLIC_GRAPHQL_SERVER_ENDPOINT'
              Value: !Ref NextPublicGraphqlServerEndpoint

Currently, the env variables in my local .env.local file, are defined as:

NEXT_PUBLIC_BASE_URL="http://localhost:3000"
NEXT_PUBLIC_SERVER_ENDPOINT="http://localhost:4000"
NEXT_PUBLIC_GRAPHQL_SERVER_ENDPOINT="http://localhost:4000/graphql"

The variables in ecs-frontend config were erroneously defined to include = signs, and it's throwing off the url, so that it is coming through as https://ui.dmphub.uc3dev.cdlib.net/=%22https://ui.dmphub.uc3dev.cdlib.net%22/apollo-csrf in the request. Will remove the = sign and the double quotes.

I didn't need to add any new env variables at this time.

[briri]

Looks good Juliet.

Go ahead and sign into AWS and copy the dev env credentials to your terminal window. Then run sceptre launch dev/regional/ecs-frontend.yaml to deploy these updates to AWS.

I'm not sure if it will automatically trigger an ECS redeploy. I think so, but give it like 10-15 minutes after you've run the Sceptre script and see if the issue is resolved. If not let me know and we can try to trigger it manually