You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In coe-alm-accelerator-templates:
Why does the template deploy-Solution.yml take importUnmanaged input parameter but rely on isUnmanaged variable to actually control the behaviour logic?
What is your question?
In coe-alm-accelerator-templates:
Why does the template deploy-Solution.yml take importUnmanaged input parameter but rely on isUnmanaged variable to actually control the behaviour logic?
This is not only very confusing but also means that the deploy-Solution.yml template is tightly coupled to Pipelines/Templates/build-deploy-Solution-To-Environment-Common.yml or Pipelines/Templates/import-Solution-To-Dev-Environment.yml as these templates are the ones setting the isUnmanaged variable.
It seems to me that it would be more intuitive to make use of the input parameter importUnmanaged to control the logic in this template.
What component are you experiencing the issue with?
ALM Accelerator Pipelines
What solution version are you using?
latest version of main branch as of October 2024.
The text was updated successfully, but these errors were encountered: