Multi-target support

[pavelkornev]

While using this specification, we imperatively found out that it may become too verbose. Being able to define an array of targets would greatly simplify some use cases. Was it considered?

Example

Current state:

overlay: 1.1.0
info:
  title: Targeted Overlay
  version: 1.0.0
actions:
  - target: $.paths['/foo'].get.description
    update: This is the updated description
  - target: $.paths['/bar'].get.description
    update: This is the updated description
  - target: $.paths['/baz'].get.description
    update: This is the updated description

Possible variation:

overlay: 1.1.0
info:
  title: Targeted Overlay
  version: 1.0.0
actions:
  - target:
    - $.paths['/foo'].get.description
    - $.paths['/bar'].get.description
    - $.paths['/baz'].get.description
    update: This is the new description

Disclaimer: the example above is intentionally artificial for simplicity reasons.

[hkosova]

You can already achieve this to an extent by using the JSONPath union selector [key1, key2]:

actions:
  - target: $.paths['/foo', '/bar', '/baz'].get
    update:
      description: This is the new description

This covers scenarios where the targets are mostly identical and differ only in a specific segment. E.g. if the targets are $.paths['/foo'] and $.paths['/bar'], but not if the targets are $.paths['/foo'] and $.components.schemas.Bar.

I've used this pattern with the bump.sh CLI, not sure if it works in other overlay implementations.

---

But I agree that a more explicit multi-target syntax would be a useful improvement.

[baywet]

@pavelkornev do you have additional scenarios that cannot already be implemented through the RFC 9535 syntax today?
Notes from the TDC today: dropping out of 1.2 milestone for now.