RWS GIS Platform Ansible Project
Categories:
GitLab: c2platform/rws/ansible-gis
The RWS GIS Platform Ansible Project is hosted on GitLab and functions as the central Ansible Inventory Project dedicated to supporting the Rijkswaterstaat (RWS) GIS Platform.
Purpose
This project has two primary objectives:
- Supporting RWS Development Environment: The RWS GIS Platform Ansible Project is an integral part of the RWS development environment, serving as a cornerstone for the RWS Ansible collections. It provides a structured inventory and automation framework that streamlines the development and management of various Ansible-based tasks and workflows within the RWS GIS Platform.
- Open-Source Reference Implementation: Beyond its role within RWS, this project also operates as an open-source reference implementation. It offers a valuable resource for showcasing diverse automation solutions and exemplifying industry best practices. By doing so, it encourages collaboration and knowledge sharing among the wider automation community.
In summary, the RWS GIS Platform Ansible Project plays a pivotal role in enhancing the efficiency of RWS operations while contributing to the broader open-source ecosystem by serving as a model for effective automation practices.
Overview
![](/images/plantuml/en/docs/gitlab/c2platform/rws/ansible-gis/_index/gis-platform.png)
How-to
Step-by-step instructions on what you can do with this project are published on C2 Platform website, see How-to Rijkswaterstaat | C2 Platform
Variables
This section provides documentation for project-specific variables utilizing the
gs_
prefix, which are introduced and employed within this inventory project.
To better understand the conventions for variable prefixes, you can refer to the
Variable prefix | C2 Platform
documentation.
gs_tomcat_https_port
Used to configure FME Flow and Tomcat:
- Run the FME Installer.
- Configure Tomcat
- Manage
fmeServerConfig.txt
gs_download_temp_dir
In this project, several roles utilized within the plays rely on the
c2platform.wincore.download
. One key variable, gs_download_temp_dir
, is defined
in group_vars/all/main.yml
, as illustrated below:
gs_download_temp_dir:
path: C:\vagrant\tmp
# create: yes
# delete: no
# recursive: true
delete_files: false
This variable is declared at the global level (in all.yml
) to ensure that its
settings can be conveniently reused throughout the inventory project. As an
example, within group_vars/fme/main.yml
, you can find the following line:
fme_flow_temp_dir: "{{ gs_download_temp_dir }}"
TODO
.sync_folders.yml voor software repo
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.