OCI DevOps Tools
*** Technology Preview ***
OCI DevOps Tools extension for Visual Studio Code provides features and tools to move and host a local Java project in the Oracle Cloud Infrastructure (OCI) DevOps service, and to perform cloud-side builds and deployments using the CI/CD pipelines.
For the best experience it is recommended to install the Graal Cloud Native Extensions Pack which contains this extension and others.
Supported Java Projects
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,
Configure OCI and OKE
Create OCI DevOps Project
Build and Deploy Project Artifacts
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.
Use an OCI Vault for a Deployed Database Application
The Graal Cloud Native Extension Pack provides an easy and secure way to run Micronaut Database applications in the Oracle Kubernetes Environment (OKE) using OCI Vault.
All details, including prerequisites, can be found in the Micronaut Tools 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
Perform Vulnerability Audits
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.
Display Related OCI DevOps Resources
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.
These additional build pipelines are preconfigured for the Java project and can be manually added to the OCI DevOps view:
Also externally created build pipelines can be added and controlled using this action.
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.
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:
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:
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:
Open OCI DevOps Resources in Oracle Cloud Console
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.
A detailed documentation on the OCI DevOps Tools extension is available here.
Provide Feedback or Seek Help
To submit a pull request for the OCI DevOps Tools extension, you need to sign the Oracle Contributor Agreement.
Project members with write access to the repository will determine and assign an appropriate Assignee for the pull request. The assignee will work with the pull request owner to address any issues and then merge the pull request.
See the CHANGELOG