From df6ca9bb47838df164290c1e1f2d43d6cea69402 Mon Sep 17 00:00:00 2001 From: Mika Rinne Date: Tue, 11 Feb 2025 17:32:55 +0200 Subject: [PATCH 1/6] readme update --- .../README.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md b/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md index 5221a020d..30ace57c1 100644 --- a/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md +++ b/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md @@ -54,7 +54,7 @@ Clone this repo locally. In OCI Console click Create Stack under OCI DevOps IAM Policies are not part of the stack, please refer to docs how to create them first.

-Important! Before running the stack it is manadatory to create the OCI Registry repository for the OCI Function container and upload a dummy X86 architecture container to it. The name of the OCIR repo needs to match to the image_name of the Stack variables e.g. helloworldai-java. The image tag must be '1'. +Important! Before running the stack it is manadatory to create the OCI Registry repository for the OCI Function container and upload a dummy X86 architecture container to it. The name of the OCIR repo needs to match to the image_name of the Stack variables e.g. helloworldai-java. The image tag must be '1'. The reason for this is that the Stack canniot create the Function without pointing to an image in OCIR.
This can by done by doing the following in OCI Cloud Shell (assuming the image name is 'helloworldai-java'): 

@@ -67,7 +67,13 @@ Unless doing this the Stack will run into an error:
 
 Error: 400-InvalidParameter, Invalid Image fra.ocir.io/<YOUR_TENANCY_NAMESPACE>/<image_name>:1 does not exist or you do not have access to use it
 

-After doing this the Stack can be run to create the OCI DevOps project. After the project creation the build pipelines can be run to build and deploy the OCI Function with real Function code.
+After doing this the Stack can be run to create the OCI DevOps project. After the project creation the build pipelines can be run to build and deploy the OCI Function with real Function code like this one (the dummy hello-world image won't run properly).
+

+The Stack creates only a private subnet in the VCN and hence the Function cannot be called outside the tenancy by default.
+However, the Function invocation can be done from OCI Cloud Shell either by connecting to the VCN private subnet or to OCI Service Network, both options will work. The invocation can be done as follows when using the Stack project_name e.g. :
+
+fn invoke helloworldai-java-project helloworldai-java-project
+

 
 # Useful Links
 

From 0bf05a27a19739c5b5ad2010145d8365b00137f4 Mon Sep 17 00:00:00 2001
From: Mika Rinne 
Date: Tue, 11 Feb 2025 17:34:10 +0200
Subject: [PATCH 2/6] readme update

---
 .../oci-devops-terraform-function-java-graalvm/README.md       | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md b/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
index 30ace57c1..f77a92f45 100644
--- a/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
+++ b/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
@@ -69,7 +69,8 @@ Error: 400-InvalidParameter, Invalid Image fra.ocir.io/<YOUR_TENANCY_NAMESPAC
After doing this the Stack can be run to create the OCI DevOps project. After the project creation the build pipelines can be run to build and deploy the OCI Function with real Function code like this one (the dummy hello-world image won't run properly).

-The Stack creates only a private subnet in the VCN and hence the Function cannot be called outside the tenancy by default. +The Stack creates only a private subnet in the VCN and hence the Function cannot be called outside the tenancy by default after the build and deploy. +
However, the Function invocation can be done from OCI Cloud Shell either by connecting to the VCN private subnet or to OCI Service Network, both options will work. The invocation can be done as follows when using the Stack project_name e.g. : 

 fn invoke helloworldai-java-project helloworldai-java-project

From 25df1fa0d85d5d7e7add61cd036b134b637ca9b5 Mon Sep 17 00:00:00 2001
From: Mika Rinne 
Date: Tue, 11 Feb 2025 17:35:35 +0200
Subject: [PATCH 3/6] readme update

---
 .../devops/oci-devops-terraform-function-java-graalvm/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md b/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
index f77a92f45..04e02da18 100644
--- a/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
+++ b/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
@@ -71,7 +71,7 @@ After doing this the Stack can be run to create the OCI DevOps project. After th
 

 The Stack creates only a private subnet in the VCN and hence the Function cannot be called outside the tenancy by default after the build and deploy.
 

-However, the Function invocation can be done from OCI Cloud Shell either by connecting to the VCN private subnet or to OCI Service Network, both options will work. The invocation can be done as follows when using the Stack project_name e.g. :
+However, the Function invocation can be done from OCI Cloud Shell either by connecting to the VCN private subnet or to OCI Service Network, both options will work. The invocation can be done as follows using the Stack project_name e.g. :
 
 fn invoke helloworldai-java-project helloworldai-java-project
 


From 554e3e86237b141eb247fc0033f1c2d7521f5e84 Mon Sep 17 00:00:00 2001
From: Mika Rinne 
Date: Tue, 11 Feb 2025 17:35:48 +0200
Subject: [PATCH 4/6] readme update

---
 .../devops/oci-devops-terraform-function-java-graalvm/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md b/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
index 04e02da18..fe4938262 100644
--- a/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
+++ b/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
@@ -56,7 +56,7 @@ OCI DevOps IAM Policies are not part of the stack, please refer to docs how to create them first.
 

-Important! Before running the stack it is manadatory to create the OCI Registry repository for the OCI Function container and upload a dummy X86 architecture container to it. The name of the OCIR repo needs to match to the image_name of the Stack variables e.g. helloworldai-java. The image tag must be '1'. The reason for this is that the Stack canniot create the Function without pointing to an image in OCIR.
+Important! Before running the stack it is manadatory to create the OCI Registry repository for the OCI Function container and upload a dummy X86 architecture container to it. The name of the OCIR repo needs to match to the image_name of the Stack variables e.g. helloworldai-java. The image tag must be '1'.
 

+The reason for this is that the Stack cannot create the Function without pointing to an image in OCIR.
+

 This can be done by doing the following in OCI Cloud Shell (assuming the image name is 'helloworldai-java'):
 
 oci artifacts container repository create --display-name helloworldai-java --compartment-id ocid1.compartment.oc1.....gq

From c5bb17d717577d1f96f326597dc55ea20b27d5c4 Mon Sep 17 00:00:00 2001
From: Mika Rinne 
Date: Tue, 11 Feb 2025 17:39:38 +0200
Subject: [PATCH 6/6] readme update

---
 .../devops/oci-devops-terraform-function-java-graalvm/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md b/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
index 783e8f9a7..e35ada877 100644
--- a/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
+++ b/app-dev/devops-and-containers/devops/oci-devops-terraform-function-java-graalvm/README.md
@@ -73,7 +73,7 @@ After doing this the Stack can be run to create the OCI DevOps project. After th
 

 The Stack creates only a private subnet in the VCN and hence the Function cannot be called outside the tenancy by default after the build and deploy.
 

-However, the Function invocation can be done from OCI Cloud Shell either by connecting to the VCN private subnet or to OCI Service Network, both options will work. The invocation can be done as follows using the Stack project_name e.g. :
+However, the Function invocation can be done from OCI Cloud Shell either by connecting to the VCN private subnet or to OCI Service Network, both options will work. The invocation can be done as follows using the Stack project_name e.g. :
 
 fn invoke helloworldai-java-project helloworldai-java-project