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
As part of the effort to make the pipeline work with 2.17.1 or later, we need to implement a short term fix. For this task, we are looking to find a way to edit and inject our exports into this dictionary, it would be easy to do but would also be an ongoing effort to keep up with community changes. If you review this the return all_vars what you will notice is the dictionary representation of the play, in the dictionary is the environment variable mapping which is empty because our framework does not use playbooks, thus we could insert/update the dictionary with our exported environment vars. See below for that snippet. By printing the vars like so:.
This task will be considered as completed once we have a working pipeline with ansible core 2.17.1 using this fix.
Ansible module
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Enabler description
Link to Epic : [Enabler] [Epic] Pipeline automation is not able to run on ansible-core 2.17.1 or later
As part of the effort to make the pipeline work with 2.17.1 or later, we need to implement a short term fix. For this task, we are looking to find a way to edit and inject our exports into this dictionary, it would be easy to do but would also be an ongoing effort to keep up with community changes. If you review this the return all_vars what you will notice is the dictionary representation of the
play
, in the dictionary is theenvironment
variable mapping which is empty because our framework does not use playbooks, thus we could insert/update the dictionary with our exported environment vars. See below for that snippet. By printing the vars like so:.This task will be considered as completed once we have a working pipeline with ansible core 2.17.1 using this fix.
Ansible module
No response
The text was updated successfully, but these errors were encountered: