Restrict ansible features to an older version?
In my work environment I have already upgraded to a newer ansible version than what co-workers have. By accident I keep using features that their version does not have yet.
Is there a way to prevent this on my side in that I force ansible to pretend it is actually an older version?
ansible ansible-2.x
add a comment |
In my work environment I have already upgraded to a newer ansible version than what co-workers have. By accident I keep using features that their version does not have yet.
Is there a way to prevent this on my side in that I force ansible to pretend it is actually an older version?
ansible ansible-2.x
any feedback on the answers?
– Kanwar Saad
Nov 21 '18 at 7:12
add a comment |
In my work environment I have already upgraded to a newer ansible version than what co-workers have. By accident I keep using features that their version does not have yet.
Is there a way to prevent this on my side in that I force ansible to pretend it is actually an older version?
ansible ansible-2.x
In my work environment I have already upgraded to a newer ansible version than what co-workers have. By accident I keep using features that their version does not have yet.
Is there a way to prevent this on my side in that I force ansible to pretend it is actually an older version?
ansible ansible-2.x
ansible ansible-2.x
asked Nov 14 '18 at 10:30
HaraldHarald
2,1861638
2,1861638
any feedback on the answers?
– Kanwar Saad
Nov 21 '18 at 7:12
add a comment |
any feedback on the answers?
– Kanwar Saad
Nov 21 '18 at 7:12
any feedback on the answers?
– Kanwar Saad
Nov 21 '18 at 7:12
any feedback on the answers?
– Kanwar Saad
Nov 21 '18 at 7:12
add a comment |
1 Answer
1
active
oldest
votes
You can use python virtual environments to handle multiple ansible versions. I use pyenv to manage virtualenvs. Here is how you can do it in bash on Linux:
Install pyenv:
You can change paths according to your liking if you don't want default paths.
git clone https://github.com/pyenv/pyenv.git $HOME/.pyenv
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> $HOME/.bashrc
echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> $HOME/.bashrc
echo 'if command -v pyenv 1>/dev/null 2>&1; then eval "$(pyenv init -)"; fi' >> $HOME/.bashrc
Install pyenv virtualenv for user:
git clone https://github.com/pyenv/pyenv-virtualenv.git $HOME/.pyenv/plugins/pyenv-virtualenv
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.bashrc
export PYENV_VIRTUALENV_DISABLE_PROMPT=1
Initialize pyenv environment for current shell
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
Install older ansible in one virtualenv:
pyenv virtualenv old_env
pyenv activate old_env
pip install ansible==2.4
Install newer ansible in other virtualenv:
pyenv virtualenv new_env
pyenv activate new_env
pip install ansible==2.7
Daily Usage:
You can switch between virtualenvs whenver you want. e.g. to switch to old ansible virtualenv and check ansible version, you can do like this:
pyenv activate old_env
ansible --version
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53298058%2frestrict-ansible-features-to-an-older-version%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can use python virtual environments to handle multiple ansible versions. I use pyenv to manage virtualenvs. Here is how you can do it in bash on Linux:
Install pyenv:
You can change paths according to your liking if you don't want default paths.
git clone https://github.com/pyenv/pyenv.git $HOME/.pyenv
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> $HOME/.bashrc
echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> $HOME/.bashrc
echo 'if command -v pyenv 1>/dev/null 2>&1; then eval "$(pyenv init -)"; fi' >> $HOME/.bashrc
Install pyenv virtualenv for user:
git clone https://github.com/pyenv/pyenv-virtualenv.git $HOME/.pyenv/plugins/pyenv-virtualenv
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.bashrc
export PYENV_VIRTUALENV_DISABLE_PROMPT=1
Initialize pyenv environment for current shell
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
Install older ansible in one virtualenv:
pyenv virtualenv old_env
pyenv activate old_env
pip install ansible==2.4
Install newer ansible in other virtualenv:
pyenv virtualenv new_env
pyenv activate new_env
pip install ansible==2.7
Daily Usage:
You can switch between virtualenvs whenver you want. e.g. to switch to old ansible virtualenv and check ansible version, you can do like this:
pyenv activate old_env
ansible --version
add a comment |
You can use python virtual environments to handle multiple ansible versions. I use pyenv to manage virtualenvs. Here is how you can do it in bash on Linux:
Install pyenv:
You can change paths according to your liking if you don't want default paths.
git clone https://github.com/pyenv/pyenv.git $HOME/.pyenv
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> $HOME/.bashrc
echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> $HOME/.bashrc
echo 'if command -v pyenv 1>/dev/null 2>&1; then eval "$(pyenv init -)"; fi' >> $HOME/.bashrc
Install pyenv virtualenv for user:
git clone https://github.com/pyenv/pyenv-virtualenv.git $HOME/.pyenv/plugins/pyenv-virtualenv
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.bashrc
export PYENV_VIRTUALENV_DISABLE_PROMPT=1
Initialize pyenv environment for current shell
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
Install older ansible in one virtualenv:
pyenv virtualenv old_env
pyenv activate old_env
pip install ansible==2.4
Install newer ansible in other virtualenv:
pyenv virtualenv new_env
pyenv activate new_env
pip install ansible==2.7
Daily Usage:
You can switch between virtualenvs whenver you want. e.g. to switch to old ansible virtualenv and check ansible version, you can do like this:
pyenv activate old_env
ansible --version
add a comment |
You can use python virtual environments to handle multiple ansible versions. I use pyenv to manage virtualenvs. Here is how you can do it in bash on Linux:
Install pyenv:
You can change paths according to your liking if you don't want default paths.
git clone https://github.com/pyenv/pyenv.git $HOME/.pyenv
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> $HOME/.bashrc
echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> $HOME/.bashrc
echo 'if command -v pyenv 1>/dev/null 2>&1; then eval "$(pyenv init -)"; fi' >> $HOME/.bashrc
Install pyenv virtualenv for user:
git clone https://github.com/pyenv/pyenv-virtualenv.git $HOME/.pyenv/plugins/pyenv-virtualenv
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.bashrc
export PYENV_VIRTUALENV_DISABLE_PROMPT=1
Initialize pyenv environment for current shell
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
Install older ansible in one virtualenv:
pyenv virtualenv old_env
pyenv activate old_env
pip install ansible==2.4
Install newer ansible in other virtualenv:
pyenv virtualenv new_env
pyenv activate new_env
pip install ansible==2.7
Daily Usage:
You can switch between virtualenvs whenver you want. e.g. to switch to old ansible virtualenv and check ansible version, you can do like this:
pyenv activate old_env
ansible --version
You can use python virtual environments to handle multiple ansible versions. I use pyenv to manage virtualenvs. Here is how you can do it in bash on Linux:
Install pyenv:
You can change paths according to your liking if you don't want default paths.
git clone https://github.com/pyenv/pyenv.git $HOME/.pyenv
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> $HOME/.bashrc
echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> $HOME/.bashrc
echo 'if command -v pyenv 1>/dev/null 2>&1; then eval "$(pyenv init -)"; fi' >> $HOME/.bashrc
Install pyenv virtualenv for user:
git clone https://github.com/pyenv/pyenv-virtualenv.git $HOME/.pyenv/plugins/pyenv-virtualenv
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.bashrc
export PYENV_VIRTUALENV_DISABLE_PROMPT=1
Initialize pyenv environment for current shell
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
Install older ansible in one virtualenv:
pyenv virtualenv old_env
pyenv activate old_env
pip install ansible==2.4
Install newer ansible in other virtualenv:
pyenv virtualenv new_env
pyenv activate new_env
pip install ansible==2.7
Daily Usage:
You can switch between virtualenvs whenver you want. e.g. to switch to old ansible virtualenv and check ansible version, you can do like this:
pyenv activate old_env
ansible --version
answered Nov 14 '18 at 12:26
Kanwar SaadKanwar Saad
1,00811223
1,00811223
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53298058%2frestrict-ansible-features-to-an-older-version%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
any feedback on the answers?
– Kanwar Saad
Nov 21 '18 at 7:12