When working behind a proxy server then VS Code Proxy has to be set ON. In VS Code Settings set Http: Proxy Support to ON.

Many tools used to work on Java projects, such as Git, Maven, Gradle, kubectl, and docker (if used), may require proxy configuration as well.

Configure OCI

• Create Oracle Cloud account, free tier is supported
• Setup an API Key for accessing the Oracle Cloud
• Create .oci/config cloud access configuration file
• Install OCI CLI needed for the OKE local access

Configure OKE

• Create and setup local access to an OKE cluster, Oracle's managed Kubernetes service

  • Use the Quick create option in the Create cluster wizard

  • Configure local access to the OKE Kubernetes cluster using the VNC-Native Public Endpoint. This is done using the Oracle Cloud Infrastructure CLI and you may have already done this in the prerequisite steps.

  

• Open a local folder containing a supported Java project
• In the Explorer activity, find the OCI DevOps view and click the Create OCI DevOps Project button
• Confirm pushing the local sources to a remote OCI code repository
• Choose the OCI profile to be used for OCI access if multiple profiles are defined
• Select target OCI Compartment for the project
• Select an existing OKE Cluster or create a new one.
• Provide a name for the DevOps Project to be created, must be unique within the Tenancy
• If requested, confirm the SSH keys for Git operations and add the Oracle Cloud Infrastructure DevOps Git server to your SSH config and known_hosts file.
• Wait for the DevOps Project and the related resources to be created.

Once an OCI DevOps Project is created, the OCI DevOps view is populated by items representing remote build and deployment pipelines for each project container artifact.

To build a project container artifact, invoke the Run Build Pipeline action for the appropriate build pipeline item. The remote build pipeline is started and VS Code displays its state and build log. After a successful build, either use the Pull Container Image action to pull the resulting container artifact locally, or proceed to deploying the container to OKE.

To deploy a built container artifact, invoke the Run Deployment Pipeline action for the appropriate deployment pipeline item. The remote deployment pipeline is started and VS Code displays its state and deployment log. After a successful deployment, use the Open In Browser action to set up a port forward from OKE and open the deployed application in web browser.

To quickly redeploy latest build, invoke the Redeploy Latest Build action. This will delete the existing pods and pull the new container image. The Redeploy Latest Build action always uses the latest deployment manifest, which is the result of the most recent successful deployment pipeline. After a successful redeployment, shorcut for Open In Browser action is provided for easy access.

Use an OCI Vault for a Deployed Database Application

The Graal Development Kit for Micronaut Extension Pack provides an easy and secure way to run Micronaut Database applications in the Oracle Kubernetes Environment (OKE) using OCI Vault.

1. Install the Graal Development Kit for Micronaut Extension Pack.

2. GDK or Micronaut application is already deployed to OCI DevOps service using this extension

3. Right-click on a database name in the Databases panel and choose Add to OCI Vault. Follow the steps.

   

All details, including prerequisites, can be found in the Tools for Micronaut® framework extension documentation. See the section Use OCI Vault to Store Database Connection Properties.

This action creates new a project artifact named <project_name>_oke_configmap, which contains the datasources.default.* properties stored in your OCI Vault. It also extends both predefined Deployment Pipelines to use this Kubernetes manifest in order to run a database application in OKE in a secure and seamless way.

As soon as a new DevOps Project is created, an audit for vulnerabilities in third-party project libraries is automatically performed. The audit can also be invoked on demand using the VS Code Command Palette, OCI DevOps: Audit Project Vulnerability command, or from a Java Projects view using the Run Project Audit action.

Vulnerability audits can also be performed for the Maven and Gradle Java projects not added to an OCI DevOps Project. Use VS Code Settings, Oci > Devops: Shared Knowledge Base Ocid and Oci > Devops: Shared Knowledge Base Profile to configure the shared Knowledge Base for performing these audits.

Initially only items for build and deployment pipelines related to project container artifacts are displayed in the OCI DevOps view. Additional resources can be manually added using the Add OCI DevOps Resource... action displayed in the view caption.

Build Pipelines

These additional build pipelines are preconfigured for the Java project and can be manually added to the OCI DevOps view:

• Build Fat Jar: builds a single application JAR file
• Build Native Executable: builds a Linux x86 native executable of an application

Also externally created build pipelines can be added and controlled using this action.

Deployment Pipelines

All preconfigured deployment pipelines are visible in the OCI DevOps view by default. Externally created build pipelines can be added and controlled using this action. Also, a new deployment pipeline can be created and added to the view, deploying a container to the OKE.

Artifact Repository

An artifact repository configured for the DevOps Project can be added to display the non-container artifacts built for the project. These actions are available for an Artifact Repository:

• Display non-container artifacts, including build date and size
• Download built non-container artifacts locally

Container Repository

Container repositories configured for a DevOps project can be added to display the container images built for the project. These actions are available for a Container Repository:

• Display container repository and the images, including a build date
• Pull container images locally

Knowledge Base

A knowledge base configured for a DevOps project can be added to display the vulnerability audits performed for the project. These actions are available for a Knowledge Base:

• Display vulnerability reports, including an audit date and result
• Shortcut to a detailed online report

Whenever a DevOps resource has a dedicated view in the Oracle Cloud Console, it can be easily displayed there using the Open in Oracle Cloud Console action available for the appropriate item in the OCI DevOps view.