OAC Snapshot Automation
Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):
Description (Required):
Currently, OAC Snapshots can be automated using REST API, however, this model needs multiple teams' intervention like IDCS, and also Access token-based authentication is inconsistent and timing out randomly
Hence,
- Snapshot creation is to be driven through a scheduler in the OAC itself.
- Should have the option to specify no. of old snapshots that can be stored.
- Snapshots can be downloaded to a designated storage area as a result of being removed from the Cloud storage or optionally at the behest of the Administrator.
Use Case and Business Need (Required):
The current Rest API method requires several labor-intensive steps, Hence simpler options in OAC itself idle and will increases user-friendliness.
Enhancement Request / Service Request:
Comments
-
Agreed. The mechanism for setting up the REST API OAUTH configuration is too complicated. Allow for setting up a bucket for the OAC instance and scheduling the snapshot to be exported there.
0 -
Agree.
Snapshot creation and maintenance needs to be driven from with in the application.
OAUTH is no suitable for a production system.
0
