Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"oJob options" not handling args expressions #653

Closed
nmaguiar opened this issue Aug 8, 2023 · 0 comments
Closed

"oJob options" not handling args expressions #653

nmaguiar opened this issue Aug 8, 2023 · 0 comments
Assignees
Labels

Comments

@nmaguiar
Copy link
Collaborator

nmaguiar commented Aug 8, 2023

Description
When using a "oJob options" where the args of a specific target job, to be called given an option, is an expression it doesn't seem to get processed (initially reported by @abrizida)

To Reproduce
Steps to reproduce the behavior:

  1. Build an oJob similar to:
todo:
- (optionOn): opt
  ((todos )):
    start:
    - name: test
      args: |
        [{ a: 1 }, { a: 2 }, { a: 3 }]

jobs:
- name: test
  exec: |
    print("A = " + args.a)
  1. Execute it with ojob test.yaml opt=start
  2. Observe that the job "test" is not correctly invoked.

Expected behavior
It would be expected that the job "test" executed 3 times with the different values of a from the array set as an expression.

Additional context
n/a

@nmaguiar nmaguiar added the bug label Aug 8, 2023
@nmaguiar nmaguiar self-assigned this Aug 8, 2023
@nmaguiar nmaguiar added this to Backlog in Continuous Enhancement via automation Aug 8, 2023
nmaguiar added a commit that referenced this issue Aug 8, 2023
nmaguiar added a commit to OpenAF/oJob-common that referenced this issue Aug 8, 2023
@nmaguiar nmaguiar mentioned this issue Aug 13, 2023
Merged
Continuous Enhancement automation moved this from Backlog to Done Oct 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

1 participant