openstack/kayobe
Code Issues Proposed changes

Fix two links in the docs pointing to repo on github (moved to opendev)

Browse Source 
Change-Id: I793251519a5da0e3d1225673c9b3394e738f4336
Signed-off-by: Radosław Piliszek <radoslaw.piliszek@gmail.com>
This commit is contained in:
Radosław Piliszek
2019-05-24 16:56:04 +02:00
parent 4495910428
commit d8c6fa307f
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/configuration/kayobe.rst
View File

@@ -62,7 +62,7 @@ variables.
Configuring Kayobe Configuring Kayobe
================== ==================
The `kayobe-config <https://github.com/openstack/kayobe-config>`_ git The `kayobe-config <https://opendev.org/x/kayobe-config>`_ git
repository contains a Kayobe configuration directory structure and unmodified repository contains a Kayobe configuration directory structure and unmodified
configuration files. This repository can be used as a mechanism for version configuration files. This repository can be used as a mechanism for version
controlling Kayobe configuration. As Kayobe is updated, the configuration controlling Kayobe configuration. As Kayobe is updated, the configuration

2
doc/source/upgrading.rst
View File

@@ -79,7 +79,7 @@ Migrating Kayobe Configuration
Kayobe configuration options may be changed between releases of kayobe. Ensure Kayobe configuration options may be changed between releases of kayobe. Ensure
that all site local configuration is migrated to the target version format. If that all site local configuration is migrated to the target version format. If
using the `kayobe-config <https://github.com/openstack/kayobe-config>`_ git using the `kayobe-config <https://opendev.org/x/kayobe-config>`_ git
repository to manage local configuration, this process can be managed via git. repository to manage local configuration, this process can be managed via git.
For example, to fetch version 1.0.0 of the configuration from the ``origin`` For example, to fetch version 1.0.0 of the configuration from the ``origin``
remote and merge it into the current branch:: remote and merge it into the current branch::