Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Manage Extension Lifecycle issues
Summary:
Manage Extension Lifecycle issues
Content (please ensure you mask any confidential information):
Hi Experts,
I have disabled CI/CD pipeline to use Manage Extension Lifecycle instead.
But we have identified a few issues/questions regarding the new Manage Extension Lifecycle page:
1. When I enable branch protection for the main branch, the new extension is not exposed in the target instance and not visible on the Manage Extension Lifecycle page even after a merge request is completed.
2. Without merge requests, the extensions are visible in the new Manage Extension Lifecycle but there is no way to identify which extension belongs to which redwood page.
0