feat(cli): allow backend service to not expose any port

[iamhopaul123]

fix #1435.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[iamhopaul123]

Manual Test

Manifest

# The manifest for the "test" service.
# Read the full specification for the "Backend Service" type at:
#  https://github.com/aws/copilot-cli/wiki/Manifests#backend-svc

# Your service name will be used in naming your resources like log groups, ECS services, etc.
name: test
# Your service does not allow any traffic.
type: Backend Service

image:
  # Docker build arguments. You can specify additional overrides here. Supported: dockerfile, context, args
  build: Dockerfile

# Number of CPU units for the task.
cpu: 256
# Amount of memory in MiB used by the task.
memory: 512
# Number of tasks that should be running in your service.
count: 1

After deployment

✔ Deployed test.

svc show

Which service of my-project would you like to show? test
About

  Application       my-project
  Name              test
  Type              Backend Service

Configurations

  Environment       Tasks               CPU (vCPU)          Memory (MiB)        Port
  test              1                   0.25                512                 -

Service Discovery

  Environment       Namespace

Variables

  Name                                Environment         Value
  COPILOT_APPLICATION_NAME            test                my-project
  COPILOT_ENVIRONMENT_NAME            test                test
  COPILOT_LB_DNS                      test                my-pr-Publi-1UZT971FFE5I-1512931134.us-west-2.elb.amazonaws.com
  COPILOT_SERVICE_DISCOVERY_ENDPOINT  test                my-project.local
  COPILOT_SERVICE_NAME                test                test

[kohidave]

Can you ensure that you can add a port after the service is created w/o a port and that service discovery works, please?

[iamhopaul123]

Can you ensure that you can add a port after the service is created w/o a port and that service discovery works, please?

It works! I tested on the multi-svc-app e2e suite (deploy frontend and backend with no port first, then redeploy backend with port 80)

[huanjani]

LGTM!

[hnrc]

As far as I'm concerned this also closes #1246 😄

[efekarakus]

@hnrc yay! how do you do the "SNS <-> SQS <-> Service" integration today?

[hnrc]

@efekarakus SNS and SQS is managed by Cloudformation and Service is just a dumb infinite loop polling SQS.