In a particular cases bundle generate job --existing-job-id and UI giving different results for job resource names.
If job name starts with a special symbol, for example job name - "[TEST] Some Name", UI will set resource name as "TEST_Some_Name" in "View YAML/JSON"
And bundle generate will call it - "_test__some_name"
In general its not a big deal, at least untill you will try to ref this job in a run_job_task.
So as far as you will try to use ${resources.jobs._test__some_name.id} it will fail
Once the underscore is removed from the beginning of the resource name - deployment will start working without issues (file itself and resource name in it obviously renamed as well)
Althought terraform support underscores in the beggining of the resource names, probably its just easier to use same pattern for name normalizationas in UI?
Steps to reproduce the behavior
Please list the steps required to reproduce the issue, for example:
Create a job with name strating from any special symbol
Run bundle generate job --existing-job-id
Resource name will start with underscore
Expected Behavior
Most likely if job name strating from a special symbol it should be truncated as it done in the UI.
Actual Behavior
Special symbol in beginning of the name converted to underscore as others.
Describe the issue
In a particular cases
bundle generate job --existing-job-idand UI giving different results for job resource names.If job name starts with a special symbol, for example job name - "[TEST] Some Name", UI will set resource name as "TEST_Some_Name" in "View YAML/JSON"
And bundle generate will call it - "_test__some_name"
In general its not a big deal, at least untill you will try to ref this job in a run_job_task. So as far as you will try to use ${resources.jobs._test__some_name.id} it will fail
Once the underscore is removed from the beginning of the resource name - deployment will start working without issues (file itself and resource name in it obviously renamed as well)
Althought terraform support underscores in the beggining of the resource names, probably its just easier to use same pattern for name normalizationas in UI?
Steps to reproduce the behavior
Please list the steps required to reproduce the issue, for example:
bundle generate job --existing-job-idExpected Behavior
Most likely if job name strating from a special symbol it should be truncated as it done in the UI.
Actual Behavior
Special symbol in beginning of the name converted to underscore as others.
OS and CLI version
cli 0.222, tested on 0.214 and 0.215