Skip to content

Commit fe053f7

Browse files
authored
Update README.md
Increment release number for magic deploy button (2.1.3).
1 parent 1d97d0c commit fe053f7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ This template deploys the following:
6868

6969
Simply click the Deploy to OCI button to create an ORM stack, then walk through the menu driven deployment. Once the stack is created, use the Terraform Actions drop-down menu to Plan, then Apply the stack.
7070

71-
[![Deploy to Oracle Cloud](https://oci-resourcemanager-plugin.plugins.oci.oraclecloud.com/latest/deploy-to-oracle-cloud.svg)](https://cloud.oracle.com/resourcemanager/stacks/create?region=home&zipUrl=https://github.com/oracle-quickstart/oke-airflow/archive/2.1.2.zip)
71+
[![Deploy to Oracle Cloud](https://oci-resourcemanager-plugin.plugins.oci.oraclecloud.com/latest/deploy-to-oracle-cloud.svg)](https://cloud.oracle.com/resourcemanager/stacks/create?region=home&zipUrl=https://github.com/oracle-quickstart/oke-airflow/archive/2.1.3.zip)
7272

7373
## Remote-exec vs. CloudInit
7474
This template allows for both remote-exec and CloudInit based deployments. By default it uses remote-exec, which uses the bastion host as an intermediary to run deployment commands using SSH. Alternatively this can be disabled, which allows for CloudInit based deployment. CloudInit packs all deployment commands into the bastion host metadata, and executes at host build time. This permits deployment with zero internet exposure, entirely on private subnet if desired. Disabling the remote-exec option during stack setup will unlock options for CloudInit based deployment.

0 commit comments

Comments
 (0)