The Oracle Analytics Cloud plugin provides operations to manage the build and deployment of WebCatalog objects across your cloud instances.
Supported Versions
- OAC for Oracle Cloud Applications
Key Features
- Source WebCatalog from SCM or Development environment.
- Supports FlexDeploy Full as well as Partial Deployments for WebCatalog objects.
- Partial deployment option allows users to select various catalog objects (via FlexDeploy package) for build and deployment. Change detection and reporting are maintained for each individual object.
- Partial deployment option can leverage dynamic packages for an effective way to manage consistent deployments at the folder level.
- When sourcing from OAC development instance, files are populated with an extension mapping to its type.
- Folders are automatically deployed first without children, followed by their components
- Operations to support synching WebCatalog objects to a source code repository.
Plugin Operations
Partial Deployments
The Oracle Analytics Cloud plugin supports full as well as partial deployment projects. Partial deployment project can be created with the "Oracle Analytics Cloud" type to manage object types defined in the next section.
- WebCatalog objects can be either sourced from the Backend (Oracle Analytics Cloud development instance) or SCM (any supported SCM type).
- Select SCM Type as None, if you want to source directly from your development environment and deploy to other environments. Keep in mind that artifacts are still captured at build time in the FlexDeploy repository to allow for reproducible deployments.
- Folder deployment in partial deployment mode only deploys the Folder without any of its children objects. You can select individual children objects as necessary in the package for deployment.
- Objects in the files list can not be sequenced for this project type. If necessary, the user can control sequencing when building user-managed packages.
- See the appendix for more details on how you can source files from SCM.
- OAC project packages are deployed using a "stop on failure" method. In other words, if any file in the package fails the other will not be attempted. The predominant reason is to avoid dozens of failures when the deployment of the parent folder fails.
Appendix