Resource Type: pulp_rpmrepo
- Defined in:
- lib/puppet/type/pulp_rpmrepo.rb
- Providers:
-
api
Overview
doc
Properties
-
allowed_keys
List of allowed signature keys that imported packages can be signed with. Comma separated values.
-
auth_ca
full path to the CA certificate that should be used to verify client authentication certificates; setting this turns on client authentication for the repository
-
auth_cert
full path to the entitlement certificate that will be given to bound consumers to grant access to this repository
-
basicauth_pass
password used to authenticate with sync location via HTTP basic auth
-
basicauth_user
username used to authenticate with sync location via HTTP basic auth
-
checksum_type
type of checksum to use during metadata generation
-
description
user-readable description (may contain i18n characters)
-
display_name
user-readable display name (may contain i18n characters)
-
download_policy
content downloading policy
Supported values:- immediate
- background
- on_demand
-
ensure
(defaults to: present)
Create/Remove pulp rpm repo.
Supported values:- present
- absent
-
feed
URL of the external source repository to sync
-
feed_ca_cert
full path to the CA certificate that should be used to verify the external repo server’s SSL certificate
-
feed_cert
full path to the certificate to use for authorization when accessing the external feed
-
feed_key
full path to the private key for feed_cert
-
generate_sqlite
if “true”, sqlite files will be generated for the repository metadata during publish
-
gpg_key
File containing public GPG keys used to validate the signatures of RPMs and metadata in this repository. These keys will be made available to consumers to use for verifying content in the repository. The value provided to this option must be the full path to a GPG key file containing one or more ASCII armored public keys.
-
host_ca
full path to the CA certificate that signed the repository hosts’s SSL certificate when serving over HTTPS
-
max_downloads
maximum number of downloads that will run concurrently
Supported values:- /^\d+$/
-
max_speed
maximum bandwidth used per download thread, in bytes/sec, when synchronizing the repo
Supported values:- /^\d+$/
-
note
adds/updates/deletes notes to programmatically identify the resource
-
proxy_host
proxy server url to use
-
proxy_pass
password used to authenticate with the proxy server
-
proxy_port
port on the proxy server to make requests
Supported values:- /^\d+$/
-
proxy_user
username used to authenticate with the proxy server
-
relative_url
relative path the repository will be served from. Only alphanumeric characters, forward slashes, underscores and dashes are allowed.
-
remove_missing
if “true”, units that were previously in the external feed but are no longer found will be removed from the repository
-
repoview
if “true”, static HTML files will be generated during publish by the repoview tool for faster browsing of the repository. Enables –generate-sqlite flag.
-
require_signature
if “Require that imported packages should be signed.
-
retain_old_count
count indicating how many non-latest versions of a unit to keep in a repository
Supported values:- /^\d+$/
-
serve_http
if “true”, the repository will be served over HTTP
-
serve_https
if “true”, the repository will be served over HTTPS
-
skip
comma-separated list of types to omit when synchronizing, if not specified all types will be synchronized; valid values are: rpm, drpm, distribution, erratum
Supported values:- rpm
- drpm
- distribution
- erratum
-
updateinfo_checksum_type
type of checksum to use during updateinfo.xml generation
-
validate
if “true”, the size and checksum of each synchronized file will be verified against the repo metadata
-
verify_feed_ssl
if “true”, the feed's SSL certificate will be verified against the feed_ca_cert
Parameters
-
conf_file
(defaults to: /etc/pulp/admin/admin.conf)
path to pulp-admin’s config file. Defaults to /etc/pulp/admin/admin.conf
-
name (namevar)
repo-id: uniquely identifies the rpm repo
-
provider
The specific backend to use for this ‘pulp_rpmrepo` resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.