Skip to content

'st2cd' shouldn't set any version variables in K/V #289

@arm4b

Description

@arm4b

Example: during the release machinery we set st2_stable_version in K/V and rely on it.

With the new st2cicd server, which could be re-provisioned anytime by us, this becomes a problem to update ops-infra Ansible repo with the new K/V value (infra-as-a-code 👊 ).
Example: https://github.com/StackStorm/ops-infra/pull/186 👎

The solution is to commit the version used directly to st2cd repo itself instead of K/V, same as we do via automation:
2c19af5

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions