Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
arm4b opened this issue Jun 16, 2017 · 0 comments
Open

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

arm4b opened this issue Jun 16, 2017 · 0 comments

Comments

@arm4b
Copy link
Member

arm4b commented Jun 16, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant