From d29396fc4289c438efab1039a77adc37f7aee40a Mon Sep 17 00:00:00 2001 From: Mika Rinne Date: Sat, 15 Feb 2025 07:36:47 +0200 Subject: [PATCH 1/5] readme instructions added for OCIR Docker login with auth token --- .../oci-devops-terraform-function-java-graalvm/README.md | 5 ++++- 1 file changed, 4 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 8b8ab8948..10fa7f9c9 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 @@ -70,9 +70,12 @@ Creating the stack in OCI Resource Manger fill in the vars:
  • initial_image that is used to create the OCI Function as target environment for the OCI DevOps deployment pipeline. By default it is loaded from Dockerhub, but you can use any X86 arch image if want to replace this
  • docker_user is your OCIR Docker user to push the initial image (above) to OCIR repo for the Function. Replace <namespace> with your tenancy namespace. oracleidentitycloudservice is only used for federated domains/users, not local
    • -
  • docker_password is your OCIR Docker user password (your user profile auth token in OCI)
    • +
  • docker_password is an auth token in your OCI user profile, create one for this +Docker credentials are only used during the DevOps project creation to push the initial Function image and the DevOps project won't need them after it's been created by Terraform. Hence, you can delete the auth token from your profile after the stack has been run. +

    + After creation run Stacks's Apply to create the OCI DevOps project.

    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. From 80a0d34bbed1a7bc083b2da00b8dd9d605919d13 Mon Sep 17 00:00:00 2001 From: Mika Rinne Date: Sat, 15 Feb 2025 07:38:27 +0200 Subject: [PATCH 2/5] readme instructions added for OCIR Docker login with auth token --- .../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 10fa7f9c9..b788339a3 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 @@ -70,7 +70,7 @@ Creating the stack in OCI Resource Manger fill in the vars:

  • initial_image that is used to create the OCI Function as target environment for the OCI DevOps deployment pipeline. By default it is loaded from Dockerhub, but you can use any X86 arch image if want to replace this
  • docker_user is your OCIR Docker user to push the initial image (above) to OCIR repo for the Function. Replace <namespace> with your tenancy namespace. oracleidentitycloudservice is only used for federated domains/users, not local
    • -
  • docker_password is an auth token in your OCI user profile, create one for this +
  • docker_password is an auth token in your OCI user profile, create one for this
    • Docker credentials are only used during the DevOps project creation to push the initial Function image and the DevOps project won't need them after it's been created by Terraform. Hence, you can delete the auth token from your profile after the stack has been run. From 0308bbb928091d8e73aaca7ff1f2cfd9efde2df6 Mon Sep 17 00:00:00 2001 From: Mika Rinne Date: Sat, 15 Feb 2025 07:39:59 +0200 Subject: [PATCH 3/5] readme instructions added for OCIR Docker login with auth token --- .../oci-devops-terraform-function-java-graalvm/README.md | 4 ++-- 1 file changed, 2 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 b788339a3..fd14a9379 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 @@ -79,8 +79,8 @@ Docker credentials are only used during the DevOps project creation to push the After creation run Stacks's Apply to create the OCI DevOps project.

    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 helloworldai-java
    From 22e62848cbaa61ff4df42d9c3e0a949bd41079d7 Mon Sep 17 00:00:00 2001 From: Mika Rinne Date: Sat, 15 Feb 2025 07:50:01 +0200 Subject: [PATCH 4/5] readme instructions added for OCIR Docker login with auth token --- .../oci-devops-terraform-function-java-graalvm/README.md | 5 +++++ 1 file changed, 5 insertions(+) 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 fd14a9379..d0b1eb3ea 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 @@ -85,6 +85,11 @@ However, the Function invocation can be done from OCI Cloud Shell e fn invoke helloworldai-java helloworldai-java +Since the stack creates this DevOps project target Function with the intial image it should already run and return: +
    +Hello, world!
+
    + # Useful Links - [OCI DevOps](https://www.oracle.com/cloud/cloud-native/devops-service/) From fecad0dae860a9a5ab927215e4d958f6ff4a012a Mon Sep 17 00:00:00 2001 From: Mika Rinne Date: Sat, 15 Feb 2025 07:51:17 +0200 Subject: [PATCH 5/5] readme instructions added for OCIR Docker login with auth token --- .../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 d0b1eb3ea..9268c296c 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 @@ -85,7 +85,7 @@ However, the Function invocation can be done from OCI Cloud Shell e fn invoke helloworldai-java helloworldai-java -Since the stack creates this DevOps project target Function with the intial image it should already run and return: +Since the stack creates the DevOps project with a target Function with the intial image it should already run and return: 
     Hello, world!