The architecture type supported by the software source.
Availability of the software source (for non-OCI environments).
Availability of the software source (for OCI environments).
The yum repository checksum type used by this software source.
The OCID of the compartment that contains the software source.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example: {@code {"Operations": {"CostCenter": "42"}}}
User-specified description for the software source.
User-friendly name for the software source.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example: {@code {"Department": "Finance"}}
Fingerprint of the GPG key for this software source.
ID of the GPG key for this software source.
URL of the GPG key for this software source.
The OCID of the software source.
Indicates whether the service should automatically resolve package dependencies when including specific packages in the software source.
Indicates whether the service should automatically update the custom software source to use the latest package versions available. The service reviews packages levels once a day.
Indicates whether the service should create the software source from a list of packages provided by the user.
Indicates whether the software source will include only the latest versions of content from vendor software sources, while accounting for other constraints set in the custom or versioned custom software source (such as a package list or filters).
The current state of the software source.
The OS family the software source belongs to.
Number of packages the software source contains. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The packages in the software source.
The repository ID for the software source.
The size of the software source in gigabytes (GB). Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
System tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
The date and time the software source was created (in RFC 3339 format).
URL for the repository. For vendor software sources, this is the URL to the regional yum server. For custom software sources, this is 'custom/
List of vendor software sources that are used for the basis of the custom software source.
The object that defines a custom software source. A software source contains a collection of packages. For more information, see Managing Software Sources.