Commit 3329bebc authored by Piers Harding's avatar Piers Harding 🛠

ST-307 - replace broken links

parent 1ae4d97a
Pipeline #138062631 passed with stages
in 3 minutes and 18 seconds
......@@ -6,7 +6,7 @@ SKA software development is organized in agile teams.
Development team
================
See https://www.scaledagileframework.com/dev-team/
See https://www.scaledagileframework.com/agile-teams/
.. todo::
......
......@@ -598,7 +598,7 @@ Configuration of a containerised application should be managed primarily by:
Avoid passing large numbers of configuration options on the command line, and service connection information that could contain secrets such as keys and passwords should not be passed as options, as these can appear in the host OS process table.
Configuration passed into a container should not directly rely on a 3rd party secret/configuration service integration such as `vault <https://www.vaultproject.io/>`_, `consul <https://www.consul.io/>`_ or `etcd <https://etcd.readthedocs.io/en/latest/>`_. If integration with these services are required, then a sidecar configuration provider architecture should be adopted that specifically handles these environment specific issues.
Configuration passed into a container should not directly rely on a 3rd party secret/configuration service integration such as `vault <https://www.vaultproject.io/>`_, `consul <https://www.consul.io/>`_ or `etcd <https://www.etcd.io/>`_. If integration with these services are required, then a sidecar configuration provider architecture should be adopted that specifically handles these environment specific issues.
Appropriate configuration defaults should be defined in the image build as described in the earlier section on :ref:`image environment variables<header-3-environment-variables>`, along with default configuration files. These defaults should be enough to launch the application into it's minimal state unaided by specifics from the user. If this is not possible then the default action of the container should be to run the application with the ``--help`` option to start the process of informing the user what to do next.
......
......@@ -12,7 +12,7 @@ An Example C++ Project
======================
We have created a `skeleton C++ project
<https://github.com/ska-telescope/cpp_template>`_. Which should provide a full introduction to the various
<https://gitlab.com/ska-telescope/templates/cpp-template>`_. Which should provide a full introduction to the various
recommendations and requirements for the development of C++. The philosophy behind the development of this
template was to demonstrate one way to meet the project guidelines. There are probably as many ways to organise C++ projects
as there are developers there are sure to be some controversial design decisions made.
......
......@@ -73,7 +73,7 @@ We suggest that whenever possible you verify your code style and patterns in you
Instructions for how to install plugins to support this do this for Visual Studio (VS Code)
and JetBrains (WebStorm, IntelliJ IDEA etc.) are include in the ska-react-webapp-skeleton readme_ file.
.. _readme: ska-telescope/ska-react-webapp-skeleton
.. _readme: https://gitlab.com/ska-telescope/ska-react-webapp-skeleton
Dependencies
============
......
......@@ -1014,7 +1014,7 @@ Local steps
helm install --dry-run --debug ./charts/<your_chart_directory>/
- For some debugging tips refer to: `debugging tips <https://github.com/helm/helm/blob/master/docs/chart_template_guide/debugging.md>`_.
- For some debugging tips refer to: `debugging tips <https://helm.sh/docs/chart_template_guide/debugging/>`_.
- Check that your chart deploys locally (utilising minikube as per our standards) and behaves as expected
......
......@@ -203,7 +203,7 @@ Build
"""""
The build stage packages/compiles the software project into distributable units of software.
The project will be checked out at the git commit hash. This specific version of the code must then be built. Failing the build stage will stop the further steps from being executed. Where possible Semantic Versioning should be used.
To create a release a git tag should be used. `See Release Procedure <http://developer.skatelescope.org/en/latest/development/python_package_release_procedure.html>`_.
To create a release a git tag should be used. `See Release Procedure <http://developer.skatelescope.org/en/latest/development/software_package_release_procedure.html>`_.
Input
Git commit hash
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment