Skip to content

Include the Ansible automation files in the Ansible Control Host image #66

Open
@alicel

Description

@alicel

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions