You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.rst
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,22 @@ All notable changes to this project will be documented in this file.
7
7
The format is based on `Keep a
8
8
Changelog <http://keepachangelog.com/>`__.
9
9
10
+
2.4.13 - 2017-12-11
11
+
--------------------
12
+
Added
13
+
~~~~~~~~~~
14
+
* Support for Load Balancing Service operations ('oci lb')
15
+
16
+
* An example of creating a load balancer can be found a https://github.com/oracle/oci-cli/blob/master/scripts/create_load_balancer.sh
17
+
18
+
* Support for user managed boot volumes: 'oci bv boot-volume', 'oci compute instance launch --source-details', 'oci compute instance terminate --preserve-boot-volume'
19
+
* Operations which create, update or delete resources with a lifecycle-state now support a --wait-for-state option which allows you to perform the action and then wait until the resource reaches a given state
20
+
* Support for specifying --profile option through OCI_CLI_PROFILE environment variable
21
+
22
+
Changed
23
+
~~~~~~~~~~
24
+
* When listing audit events ('oci audit event list'), audit events can now have a 'response-payload' attribute which contains metadata of interest. For example, the OCID of a resource
# This script provides an example of how to create a load balancer using the CLI. Two main ways to create a load balancer are shown:
3
+
#
4
+
# - Creating a load balancer by providing all options at create time (e.g. certificates, listeners, backend sets)
5
+
# - We also show two sub-variants: providing each option as an individual parameter (e.g. --certificiates, --listeners) and how to provide a consolidated
6
+
# set of options using --from-json
7
+
# - Creating a load balancer by providing the minimum options at create time and then adding related resources (e.g. certificates, listeners, backend sets)
8
+
# post-creation
9
+
#
10
+
# Requirements for running this script:
11
+
# - OCI CLI v2.4.13 or later (you can check this by running oci --version)
12
+
# - jq (https://stedolan.github.io/jq/) for JSON querying of CLI output. This may be a useful utility in general and may help cater to scenarios
13
+
# which can't be wholly addressed by the --query option in the CLI
14
+
# - OpenSSL (for certificate generation). This is not a strict requirement for normal CLI usage, just for this demo script
15
+
# - demjson (http://deron.meranda.us/python/demjson/). This is not a strict requirement fpr normal CLI usage, it is just used to strip comments and explanatory notes from the example
16
+
# input files which support this script
17
+
18
+
COMPARTMENT_ID=""# Your compartment OCID
19
+
AVAILABILITY_DOMAIN_ONE=""# An availability domain, e.g. Uocm:IAD-AD-1
20
+
AVAILABILITY_DOMAIN_TWO=""# An availability domain, but different to AVAILABILITY_DOMAIN_TWO, e.g. Uocm:IAD-AD-2
# We need to specify a shape when creating a load balancer. Here we are just picking the first shape
35
+
# we get from listing all the available shapes
36
+
LB_SHAPE=$(oci lb shape list -c $COMPARTMENT_ID| jq -r '.data[0].name')
37
+
echo"Load Balancer Shape: $LB_SHAPE"
38
+
39
+
# A function which creates a load balancer by providing all options at create time to the oci lb load-balancer create command. This command takes multiple complex parameters (complex
40
+
# parameters are those where the CLI expects JSON to be provided as input). For ease of use, the complex parameter input will be passed in from a file rather than trying to specify
41
+
# the strings on the command line
42
+
#
43
+
# This also provides each complex type as an individual option (e.g. --certificates, --listeners). It is also possible to provide these in a consolidated format, which is demonstrated
44
+
# by the function create_lb_with_all_options_using_from_json
# certificates_with_comments.json contains a description of the parameter. Since valid JSON cannot contain comments, we use jsonlint (which was installed
47
+
# via our demjson dependency) to remove the comments and allow the CLI to use it.
48
+
#
49
+
# You should replace the values in certificates_with_comments.json with those appropriate for your use case (e.g. your own PEM-formatted strings)
# We've seen in the create_lb_with_all_options_as_individual_options function that we can create a load balancer and provide complex parameters, such as --backend-sets,
100
+
# as separate options. However, rather than specifying complex parameters individually, we can supply them in a consolidated format - in this case by passing it in
101
+
# as a single file to the --from-json option.
102
+
#
103
+
# It is actually possible to not provide individual options to CLI commands at all and pass all parameters via --from-json, but for the purposes of this example we'll
print_status("The executable directory cannot be the same as the {} directory of the virtualenv. Adding this directory to your PATH could interfere with your system python installation.".format(install_dir_bin_folder))
211
+
exec_dir=None
212
+
206
213
create_dir(exec_dir)
207
214
print_status("The executable will be in '{}'.".format(exec_dir))
0 commit comments