Delete an Extension

The method you use to delete an extension depends on if you want to delete the entire extension or only an extension version. Delete an entire extension using the Manage Lifecycle Extension page. To delete an extension version, the method is different depending on if the extension is deployed to an Oracle Cloud Applications instance that's in the same identity domain as VB Studio, or a different one.

  • You delete an extension version manually from its environment's Deployments tab, if the extension is deployed to an Oracle Cloud Applications instance that's in the same identity domain as VB Studio (by default a TEST pod, although it could be a DEV pod or a different TEST pod if you requested that Oracle re-associate VB Studio to a different pod). You could also configure a build job to delete it.

  • If the extension is deployed to a different identity domain (typically your PROD instance) and you want to delete an extension version, you must configure a build job to delete it.

Delete an Extension Manually

Use the Manage Extension Lifecycle page to delete extensions deployed from any project and to any Oracle Cloud Applications instance, provided the instance it's deployed to has an authentication method of OAuth.

If the extension was deployed to an Oracle Cloud Applications instance whose authentication method is something other than OAuth, you must either use its environment's Deployments tab to delete the extension or configure a build job to delete it.
To delete an extension using the Manage Extension Lifecycle page:
  1. Access the Manage Extension Lifecycle page:
    • From the menu in the Designer's header, click Extension Lifecycle.
    • Or, from the VB Studio left navigator, click Environments, then click Extension Lifecycle. You won't see this option if you haven't yet added an Oracle Cloud Applications instance to your environment.


      Description of mel-ui-envts.png follows
      Description of the illustration mel-ui-envts.png

    You should now see the Manage Extension Lifecycle page, which lists all the environments that are available. You can work with an environment on this page as long as the authentication method for its Oracle Cloud Applications instance is OAuth.

    Under each environment, you'll see a list of the extensions already deployed. Each entry includes the extension name plus additional details, such as extension version, deployment date, and project name. The Manage Extension Lifecycle page can show all extensions deployed from the current project or across projects. Use Show all extensions and Only show extensions for my project to toggle between both views.

  2. To delete an extension from an Oracle Cloud Applications instance, find the extension that you want to delete and click Delete Extension.

    Tip:

    Before deleting an extension from your PROD instance, delete the extension from the DEV instance (or TEST instance, if applicable) and make sure there aren't any adverse effects.

Delete an Extension Version Manually

You can delete a version of an extension from its environment's Deployments tab, if an extension is deployed to the Oracle Cloud Applications instance in the same identity domain as your VB Studio instance.

  1. In the left navigator, click Environments Environments.
  2. Select the Development environment where the extension is deployed.
  3. Click the Deployments tab.
  4. Expand the base application's name.
  5. Click Actions Three horizontal dots and select Delete next to the extension you want to delete.
    Note that there can be only one active extension version at a time. The recommended best practice is to avoid deleting the active extension version because, if you delete it, the extension will become inactive as if it wasn't installed at all. You can, however, delete inactive versions without impacting the currently active deployed extension.
  6. In the confirmation dialog box, click Delete.
For an extension deployed to an Oracle Cloud Applications instance in the same identity domain as VB Studio, you can also use a build job to delete it, if preferred.