mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-07-22 12:50:22 -07:00
Update documentation based on 301 permanent redirects (#43675)
This commit is contained in:
parent
b0542217e2
commit
00e5123e4c
25 changed files with 43 additions and 43 deletions
|
@ -38,7 +38,7 @@ instructions on how to actually use the modules and authenticate with the Azure
|
|||
Using Service Principal
|
||||
.......................
|
||||
|
||||
There is now a detailed official tutorial describing `how to create a service principal <https://azure.microsoft.com/en-us/documentation/articles/resource-group-create-service-principal-portal/>`_.
|
||||
There is now a detailed official tutorial describing `how to create a service principal <https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal>`_.
|
||||
|
||||
After stepping through the tutorial you will have:
|
||||
|
||||
|
|
|
@ -34,7 +34,7 @@ Still using Dockerfile to build images? Check out `ansible-container <https://gi
|
|||
and start building images from your Ansible playbooks.
|
||||
|
||||
Use the *shipit* command in `ansible-container <https://github.com/ansible/ansible-container>`_
|
||||
to launch your docker-compose file on `OpenShift <https://www.openshift.org/>`_. Go from an app on your laptop to a fully
|
||||
to launch your docker-compose file on `OpenShift <https://www.okd.io/>`_. Go from an app on your laptop to a fully
|
||||
scalable app in the cloud in just a few moments.
|
||||
|
||||
There's more planned. See the latest ideas and thinking at the `Ansible proposal repo <https://github.com/ansible/proposals/tree/master/docker>`_.
|
||||
|
|
|
@ -58,7 +58,7 @@ Setting the environment parameter RAX_CREDS_FILE to the path of this file will h
|
|||
this information.
|
||||
|
||||
More information about this credentials file can be found at
|
||||
https://github.com/rackspace/pyrax/blob/master/docs/getting_started.md#authenticating
|
||||
https://github.com/pycontribs/pyrax/blob/master/docs/getting_started.md#authenticating
|
||||
|
||||
|
||||
.. _virtual_environment:
|
||||
|
|
|
@ -278,7 +278,7 @@ For other load balancers, you may need to send shell commands to them (like we d
|
|||
Continuous Delivery End-To-End
|
||||
``````````````````````````````
|
||||
|
||||
Now that you have an automated way to deploy updates to your application, how do you tie it all together? A lot of organizations use a continuous integration tool like `Jenkins <http://jenkins-ci.org/>`_ or `Atlassian Bamboo <https://www.atlassian.com/software/bamboo>`_ to tie the development, test, release, and deploy steps together. You may also want to use a tool like `Gerrit <https://code.google.com/p/gerrit/>`_ to add a code review step to commits to either the application code itself, or to your Ansible playbooks, or both.
|
||||
Now that you have an automated way to deploy updates to your application, how do you tie it all together? A lot of organizations use a continuous integration tool like `Jenkins <https://jenkins.io/>`_ or `Atlassian Bamboo <https://www.atlassian.com/software/bamboo>`_ to tie the development, test, release, and deploy steps together. You may also want to use a tool like `Gerrit <https://www.gerritcodereview.com/>`_ to add a code review step to commits to either the application code itself, or to your Ansible playbooks, or both.
|
||||
|
||||
Depending on your environment, you might be deploying continuously to a test environment, running an integration test battery against that environment, and then deploying automatically into production. Or you could keep it simple and just use the rolling-update for on-demand deployment into test or production specifically. This is all up to you.
|
||||
|
||||
|
@ -296,7 +296,7 @@ This should give you a good idea of how to structure a multi-tier application wi
|
|||
An introduction to playbook roles
|
||||
:ref:`playbooks_variables`
|
||||
An introduction to Ansible variables
|
||||
`Ansible.com: Continuous Delivery <https://www.ansible.com/ansible-continuous-delivery>`_
|
||||
`Ansible.com: Continuous Delivery <https://www.ansible.com/use-cases/continuous-delivery>`_
|
||||
An introduction to Continuous Delivery with Ansible
|
||||
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ Using Vagrant and Ansible
|
|||
Introduction
|
||||
````````````
|
||||
|
||||
`Vagrant <https://vagrantup.com/>`_ is a tool to manage virtual machine
|
||||
`Vagrant <https://www.vagrantup.com/>`_ is a tool to manage virtual machine
|
||||
environments, and allows you to configure and use reproducible work
|
||||
environments on top of various virtualization and cloud platforms.
|
||||
It also has integration with Ansible as a provisioner for these virtual
|
||||
|
@ -15,7 +15,7 @@ machines, and the two tools work together well.
|
|||
This guide will describe how to use Vagrant 1.7+ and Ansible together.
|
||||
|
||||
If you're not familiar with Vagrant, you should visit `the documentation
|
||||
<https://docs.vagrantup.com/v2/>`_.
|
||||
<https://www.vagrantup.com/docs/>`_.
|
||||
|
||||
This guide assumes that you already have Ansible installed and working.
|
||||
Running from a Git checkout is fine. Follow the :ref:`installation_guide`
|
||||
|
@ -44,7 +44,7 @@ Ansible provisioner to manage a single machine:
|
|||
|
||||
# Disable the new default behavior introduced in Vagrant 1.7, to
|
||||
# ensure that all Vagrant machines will use the same SSH key pair.
|
||||
# See https://github.com/mitchellh/vagrant/issues/5005
|
||||
# See https://github.com/hashicorp/vagrant/issues/5005
|
||||
config.ssh.insert_key = false
|
||||
|
||||
config.vm.provision "ansible" do |ansible|
|
||||
|
@ -60,7 +60,7 @@ access.
|
|||
|
||||
There are a lot of Ansible options you can configure in your ``Vagrantfile``.
|
||||
Visit the `Ansible Provisioner documentation
|
||||
<https://docs.vagrantup.com/v2/provisioning/ansible.html>`_ for more
|
||||
<https://www.vagrantup.com/docs/provisioning/ansible.html>`_ for more
|
||||
information.
|
||||
|
||||
.. code-block:: bash
|
||||
|
@ -134,7 +134,7 @@ Advanced Usages
|
|||
```````````````
|
||||
|
||||
The "Tips and Tricks" chapter of the `Ansible Provisioner documentation
|
||||
<https://docs.vagrantup.com/v2/provisioning/ansible.html>`_ provides detailed information about more advanced Ansible features like:
|
||||
<https://www.vagrantup.com/docs/provisioning/ansible.html>`_ provides detailed information about more advanced Ansible features like:
|
||||
|
||||
- how to parallely execute a playbook in a multi-machine environment
|
||||
- how to integrate a local ``ansible.cfg`` configuration file
|
||||
|
@ -143,11 +143,11 @@ The "Tips and Tricks" chapter of the `Ansible Provisioner documentation
|
|||
|
||||
`Vagrant Home <https://www.vagrantup.com/>`_
|
||||
The Vagrant homepage with downloads
|
||||
`Vagrant Documentation <https://docs.vagrantup.com/v2/>`_
|
||||
`Vagrant Documentation <https://www.vagrantup.com/docs/>`_
|
||||
Vagrant Documentation
|
||||
`Ansible Provisioner <https://docs.vagrantup.com/v2/provisioning/ansible.html>`_
|
||||
`Ansible Provisioner <https://www.vagrantup.com/docs/provisioning/ansible.html>`_
|
||||
The Vagrant documentation for the Ansible provisioner
|
||||
`Vagrant Issue Tracker <https://github.com/mitchellh/vagrant/issues?q=is%3Aopen+is%3Aissue+label%3Aprovisioners%2Fansible>`_
|
||||
`Vagrant Issue Tracker <https://github.com/hashicorp/vagrant/issues?q=is%3Aopen+is%3Aissue+label%3Aprovisioners%2Fansible>`_
|
||||
The open issues for the Ansible provisioner in the Vagrant project
|
||||
:ref:`working_with_playbooks`
|
||||
An introduction to playbooks
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue