Version information
This version is compatible with:
- Puppet Enterprise 2023.8.x, 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x
- Puppet >= 6.21.0 < 9.0.0
- ,
Start using this module
Add this module to your Puppetfile:
mod 'stschulte-oracle', '2.0.0'
Learn more about managing modules with a PuppetfileDocumentation
Puppet Oracle Module
This repository aims to ease the configuration of Oracle Databases with custom types and providers
New facts
(currently none)
New functions
(currently none)
New custom types
oratab
The oratab file stores information about the home directory of your databases and whether the different instances should be automatically started and stopped by the dbstart and dbshut scripts or not.
The oratab type now allows you to treat a single entry as a resource:
oratab { 'PROD_DB':
ensure => present,
home => '/u01/app/oracle/product/10.1.0/db_1',
atboot => yes,
}
The example above will lead to the following entry in the file /etc/oratab
(or /var/opt/oracle/oratab
on Solaris)
PROD_DB:/u01/app/oracle/product/10.1.0/db_1:Y
You can also specify an inline comment with the description property. This is however optional.
oratab { 'PROD_DB':
ensure => present,
home => '/u01/app/oracle/product/10.1.0/db_1',
atboot => yes,
description => 'managed by puppet'
}
will lead to
PROD_DB:/u01/app/oracle/product/10.1.0/db_1:Y # managed by puppet
If you do not specifiy the description property, puppet will not touch the current inline comment.
This might interest you because newer versions of oracle always update the comment as
line added by agent
on each instance stop and start.
Running tests
Before running tests ensure you have all dependencies installed
bundle install
You can now generate documentation and run tests
bundle exec rake syntax lint metadata_lint check:symlinks check:git_ignore check:dot_underscore check:test_file rubocop
bundle exec rake spec
Reference
Table of Contents
Resource types
oratab
: Define database instaces in /etc/oratab with instance name home directory and a flag which indicates if the instance should be started togeth
Resource types
oratab
Define database instaces in /etc/oratab with instance name home directory and a flag which indicates if the instance should be started together with the database
Properties
The following properties are available in the oratab
type.
atboot
Valid values: yes
, no
, Y
, N
Aliases: "Y"=>"yes", "N"=>"no"
If the instance should start together with the database itself
set this property to yes
otherwise to no
description
An optional description that will be added as an inline comment in the target file
ensure
Valid values: present
, absent
The basic property that the resource should be in.
Default value: present
home
The home directory of the instance. This must be an absolute path
target
The path of the target file to store the instance information in
Parameters
The following parameters are available in the oratab
type.
name
namevar
The instance's name
provider
The specific backend to use for this oratab
resource. You will seldom need to specify this --- Puppet will usually
discover the appropriate provider for your platform.
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[Unreleased]
[2.0.0] - 2024-05-20
Added
- Support RHEL8 and CentOS 8
- Add version requirement in
metadata.json
(>= 6.21.0 < 9.0.0
)
Changed
- Update structure to work with latest puppet version
[1.0.0] - 2015-01-22
Added
- Initial release for puppet forge