oracle / oracle/oci-cli

lb listener create ignores sslConfiguration with --from-json input

Open
#603 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
669
Forks
236
Avg merge
1m
Merged PRs (30d)
4

Description

oci lb listener create --generate-full-command-json-input produces a sample json including a sslConfiguration section i.e.

{
  "cipherSuiteName": "string",
  "connectionConfigurationBackendTcpProxyProtocolVersion": 0,
  "connectionConfigurationIdleTimeout": 0,
  "defaultBackendSetName": "string",
  "hostnameNames": [
    "string",
    "string"
  ],
  "ifMatch": "string",
  "loadBalancerId": "string",
  "maxWaitSeconds": 0,
  "name": "string",
  "pathRouteSetName": "string",
  "port": 0,
  "protocol": "string",
  "protocols": [
    "string",
    "string"
  ],
  "routingPolicyName": "string",
  "ruleSetNames": [
    "string",
    "string"
  ],
  "serverOrderPreference": "string",
  "sslCertificateName": "string",
  "sslConfiguration": {
    "certificateIds": [
      "string",
      "string"
    ],
    "certificateName": "string",
    "protocols": [
      "string",
      "string"
    ],
    "trustedCertificateAuthorityIds": [
      "string",
      "string"
    ],
    "verifyDepth": 0,
    "verifyPeerCertificate": true
  },
  "sslVerifyDepth": 0,
  "sslVerifyPeerCertificate": true,
  "waitForState": [
    "ACCEPTED|IN_PROGRESS|FAILED|SUCCEEDED"
  ],
  "waitIntervalSeconds": 0
}

However, if this section is provided in the JSON input, it is ignored and a listener without SSL/TLS configuration is created.

As the OCI CLI does not seem to support the Certificate Management Service with command-line arguments, the --from-json JSON input seems to be the only way to create a listener using the Certificate Management Service (i.e. using certificate IDs - certificateIds), however, it does not work.

OCI CLI needs some way of supporting the creation of listeners that use the Certificate Management Service.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the oci lb listener create command and its --from-json input handling, focusing on the sslConfiguration field. Trace why the nested configuration is discarded, then run the relevant listener create tests or CLI validation available in the repository. Done means JSON input using certificateIds creates a listener with its SSL/TLS configuration preserved.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.