Closed dickensdjj closed 1 year ago
Hello @dickensdjj. I am not able to reproduce the problem. If you upgrade your local Copilot version to v1.30.1
can you deploy successfully? My guess is the CICD for some reason picked up a different manifest (maybe you have different manifests in different branches?) 🤔
Issue found. There is one variable that I am using and this is working perfectly in my local environment, which is MacOS "[\"test1@test.com\",\"test2@test.com\"]"
When the pipeline picks up the manifest.yml by using the Atlassian/default-image:latest, this ☝️ value will not be parsed by the YAML reader. Instead, I have to use this "['test1@test.com','test1@test.com']"
Not sure if @iamhopaul123 can reproduce this but it looks like it is the platform compatibility issue from my guess.
Context
Repo: BitBucket Secrets: AWS Secret Manager CICD Pipeline: BitBucket Pipeline Local: MacOS Local Copilot Version(copilot-darwin): 1.28.0 Bitbucket Runner: atlassian/default-image (Ubuntu 22.0.4) Runner Copilot Version(copilot-linux): 1.30.1
I am deploying a Load Balanced Web Service to the ECS cluster with Fargate via AWS copilot CLI. I am NOT using the AWS Copilot Pipeline as my CICD Pipeline because I would like to manage it via BitBucket.
Issue
The BitBucket pipeline cannot deploy the svc due to the error shown below Error: unmarshal service xxx manifest: unmarshal manifest for Load Balanced Web Service: unmarshal "variables": cannot unmarshal field to a string or into a map
This is my manifest.yml
This is my bitbucket.yml
Reference: