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
At the moment the whole zdm-proxy-automation repo is cloned into the Ansible Control Host container when this is being initialised.
This has the following implications:
The whole automation repo is made available, when only the Ansible part would be relevant.
The user can check out a different tag or branch of the automation, which breaks the versioning relationship and can cause confusion when consulting version-based docs or reporting issues.
To improve this we should directly include the Ansible scripts in the ACH image, rather than obtaining them through git, which would fix the dependency and eliminate this potential point of confusion: given the version of the image used by the ACH container, we always know the version of the automation scripts.
This ticket is part of the second (longer-term) set of changes to improve the ZDM Versioning and support version-based documentation.
┆Issue is synchronized with this Jira Task by Unito
┆Components: Automation
┆Priority: Major
The text was updated successfully, but these errors were encountered:
At the moment the whole zdm-proxy-automation repo is cloned into the Ansible Control Host container when this is being initialised.
This has the following implications:
The whole automation repo is made available, when only the Ansible part would be relevant.
The user can check out a different tag or branch of the automation, which breaks the versioning relationship and can cause confusion when consulting version-based docs or reporting issues.
To improve this we should directly include the Ansible scripts in the ACH image, rather than obtaining them through git, which would fix the dependency and eliminate this potential point of confusion: given the version of the image used by the ACH container, we always know the version of the automation scripts.
This ticket is part of the second (longer-term) set of changes to improve the ZDM Versioning and support version-based documentation.
┆Issue is synchronized with this Jira Task by Unito
┆Components: Automation
┆Priority: Major
The text was updated successfully, but these errors were encountered: