healthcheck.test does not accept string literal shorthand of CMD-SHELL

[anatawa12]

services:
  redis:
    restart: always
    image: redis:7-alpine
    volumes:
      - redis-data:/data
    healthcheck:
      test: "redis-cli ping"
      interval: 5s
      retries: 20
    ports:
      - "6379:6379"

This errors with Error: typeMismatch(Yams.Node.Sequence, Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "services", intValue: nil), _DictionaryCodingKey(stringValue: "redis", intValue: nil), CodingKeys(stringValue: "healthcheck", intValue: nil), CodingKeys(stringValue: "test", intValue: nil)], debugDescription: "Expected to decode Sequence but found Node instead.", underlyingError: nil))

test defines the command Compose runs to check container health. It can be either a string or a list. If it's a list, the first item must be either NONE, CMD or CMD-SHELL. If it's a string, it's equivalent to specifying CMD-SHELL followed by that string.

https://github.com/compose-spec/compose-spec/blob/main/05-services.md#healthcheck

container-compose v0.9.0 installed with brew

$ container-compose --version           
container-compose version 0.9.0

[roncsak]

Hi,
I am using the same version of container-compose.

I wanted to try out this awesome project based on the Develop with containers - dockerdocs and after cloning the repo and entering the command container-compose up -f compose.yaml I've got a similar error message:

Error: typeMismatch(Yams.Node.Sequence, Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "services", intValue: nil), _DictionaryCodingKey(stringValue: "backend", intValue: nil), CodingKeys(stringValue: "depends_on", intValue: nil)], debugDescription: "Expected to decode Sequence but found Node instead.", underlyingError: nil))

[Mcrich23]

Yes. The issue is health check is not currently supported, so we have not built out the parsing for it to pass all of the cases. I will look into making a quick fix regarding this.

[roncsak]

Hi @Mcrich23 ,
I am not a expert in this topic so I am just thinking whether it would be a good temporary solution catching all non-supported attributes - depends_on, healthcheck, etc - and logging a warning in the terminal that is currently not supported.
This way, users of container-compose would get a descriptive message about a certain compose attribute is not yet supported and it will be ignored.
...though I do not know ignoring an attribute is good or bad in general.

[Mcrich23]

@roncsak This already happens. However, I have not put all of the effort needed into making it always 100% of the time parse correctly. The issue here is a struct parsing issue that was neglected due to lack of support.

I will be addressing it soon since it should not be difficult to implement.