Releasing version 3.37.7

Releasing version 3.37.7

CHANGELOG.rst

@@ -6,6 +6,36 @@ All notable changes to this project will be documented in this file.
 
 The format is based on `Keep a Changelog <http://keepachangelog.com/>`__.
 
+3.37.7 - 2024-01-30
+--------------------
+Added
+~~~~~
+* Support for Capacity Management features in OCI Control Center service
+
+  * ``oci capacity-management occ-availability-catalog-collection list``
+  * ``oci capacity-management occ-availability-catalog list``
+  * ``oci capacity-management occ-capacity-request create``
+  * ``oci capacity-management occ-capacity-request delete``
+  * ``oci capacity-management occ-capacity-request get``
+  * ``oci capacity-management occ-capacity-request update``
+
+* Support for Named Credential in the Database Management service
+
+  * ``oci database-management named-credential create``
+  * ``oci database-management named-credential get``
+  * ``oci database-management named-credential list``
+  * ``oci database-management named-credential update``
+  * ``oci database-management named-credential change-compartment``
+  * ``oci database-management named-credential delete``
+  * ``oci database-management managed-database list-users --opc-named-credential-id --managed-database-id``
+
+Modified
+~~~~~~~~
+* Data integration service
+  * Support for REST connectivity with oath2
+    * ``oci data-integration data-asset create``
+
+
 3.37.6 - 2024-01-25
 --------------------
 Added

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at <opensource_ww_grp@oracle.com>. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,62 @@
+# Contributing to this repository
+
+We welcome your contributions! There are multiple ways to contribute, even if
+you're not a developer.
+
+## Opening issues
+
+If you think you've found a security vulnerability, do not open a GitHub issue.
+Instead, follow the instructions in our [security policy](./SECURITY.md).
+
+To report a bug or request an enhancement that is not related to a security
+vulnerabiliity, open a GitHub issue. When filing a bug, remember that the better
+written the bug is, the more easier and more likely it is to be reproduced and
+fixed.
+
+## Pre-requisites for code or documentation submissions
+
+Before we can review or accept any source code or documentation-related
+contribution, you will need to digitally sign the [Oracle Contributor Agreement][OCA]
+(OCA) using the OCA Signing Service. This only needs to be done once, so if
+you've signed it for another repo or project, there is no need to sign again.
+
+All your commit messages must include the following line using the same name and
+email address you used to sign the OCA:
+
+```text
+Signed-off-by: Your Name <you@example.org>
+```
+
+This can be automatically added to pull requests by committing with `--sign-off`
+or `-s`, e.g.
+
+```text
+git commit --signoff
+```
+
+We can only accept pull requests from contributors who have been verified as
+having signed the OCA.
+
+## Pull request process
+
+1. Ensure there is an issue created to track and discuss the fix or enhancement
+   you intend to submit.
+1. Fork this repository
+1. Create a branch in your fork to implement the changes. We recommend using
+   the issue number as part of your branch name, e.g. `1234-fixes`
+1. Ensure that any documentation is updated with the changes that are required
+   by your change.
+1. Ensure that any samples are updated if the base image has been changed.
+1. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
+   what your changes are meant to do and provide simple steps on how to validate
+   your changes. Ensure that you reference the issue you created as well.
+1. We will assign the pull request to specific people for review before it is merged.
+
+## Code of conduct
+
+Our [Code of Conduct](./CODE_OF_CONDUCT.md) is adapted from the
+[Contributor Covenant][CC], version 1.4, available at
+ <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>.
+
+[OCA]: https://oca.opensource.oracle.com
+[CC]: https://www.contributor-covenant.org

SECURITY.md

@@ -0,0 +1,39 @@
+# Reporting security vulnerabilities to Oracle
+
+Oracle values the independent security research community and believes that
+responsible disclosure of security vulnerabilities helps us ensure the security
+and privacy of all our users.
+
+Please do NOT raise a GitHub Issue to report a security vulnerability. If you
+believe you have found a security vulnerability, please submit a report to
+<mailto:secalert_us@oracle.com> preferably with a proof of concept. Please review
+some additional information on [how to report security vulnerabilities to Oracle][1].
+We encourage people who contact Oracle Security to use email encryption using
+[our encryption key][2].
+
+We ask that you do not use other channels or contact the project maintainers
+directly.
+
+Non-vulnerability related security issues including ideas for new or improved
+security features are welcome on GitHub Issues.
+
+## Security updates, alerts and bulletins
+
+Security updates will be released on a regular cadence. Many of our projects
+will typically release security fixes in conjunction with the
+[Oracle Critical Patch Update][3] program. Security updates are released on the
+Tuesday closest to the 17th day of January, April, July and October. A pre-release
+announcement will be published on the Thursday preceding each release. Additional
+information, including past advisories, is available on our [security alerts][3]
+page.
+
+## Security-related information
+
+We will provide security related information such as a threat model, considerations
+for secure use, or any known security issues in our documentation. Please note
+that labs and sample code are intended to demonstrate a concept and may not be
+sufficiently hardened for production use.
+
+[1]: https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html
+[2]: https://www.oracle.com/security-alerts/encryptionkey.html
+[3]: https://www.oracle.com/security-alerts/

requirements.txt

@@ -14,7 +14,7 @@ Jinja2==3.0.3
 jmespath==0.10.0
 ndg-httpsclient==0.4.2
 mock==2.0.0
-oci==2.119.1
+oci==2.120.0
 packaging==20.2
 pluggy==0.13.0
 py==1.11.0

services/capacity_management/__init__.py

@@ -0,0 +1,4 @@
+# coding: utf-8
+# Copyright (c) 2016, 2024, Oracle and/or its affiliates.  All rights reserved.
+# This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license.
+# NOTE: This class is auto generated by OracleSDKGenerator. DO NOT EDIT. API Version: 20231107

services/capacity_management/src/__init__.py

@@ -0,0 +1,4 @@
+# coding: utf-8
+# Copyright (c) 2016, 2024, Oracle and/or its affiliates.  All rights reserved.
+# This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license.
+# NOTE: This class is auto generated by OracleSDKGenerator. DO NOT EDIT. API Version: 20231107

services/capacity_management/src/oci_cli_capacity_management/__init__.py

@@ -0,0 +1,4 @@
+# coding: utf-8
+# Copyright (c) 2016, 2024, Oracle and/or its affiliates.  All rights reserved.
+# This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license.
+# NOTE: This class is auto generated by OracleSDKGenerator. DO NOT EDIT. API Version: 20231107

services/capacity_management/src/oci_cli_capacity_management/capacitymanagement_cli_extended.py

@@ -0,0 +1,53 @@
+# coding: utf-8
+# Copyright (c) 2016, 2020, Oracle and/or its affiliates.  All rights reserved.
+# This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license.
+
+import click  # noqa: F401
+import json  # noqa: F401
+from services.capacity_management.src.oci_cli_capacity_management.generated import capacitymanagement_cli
+from oci_cli import cli_util  # noqa: F401
+from oci_cli import custom_types  # noqa: F401
+from oci_cli import json_skeleton_utils  # noqa: F401
+
+
+# oci capacity-management occ-capacity-request-collection list-occ-capacity-requests -> oci capacity-management occ-capacity-request-collection list
+cli_util.rename_command(capacitymanagement_cli, capacitymanagement_cli.occ_capacity_request_collection_group, capacitymanagement_cli.list_occ_capacity_requests, "list")
+
+
+# oci capacity-management occ-capacity-request-collection list-occ-capacity-requests-internal -> oci capacity-management occ-capacity-request-collection list-internal
+cli_util.rename_command(capacitymanagement_cli, capacitymanagement_cli.occ_capacity_request_collection_group, capacitymanagement_cli.list_occ_capacity_requests_internal, "list-internal")
+
+
+# oci capacity-management occ-customer-group-collection list-occ-customer-groups -> oci capacity-management occ-customer-group-collection list
+cli_util.rename_command(capacitymanagement_cli, capacitymanagement_cli.occ_customer_group_collection_group, capacitymanagement_cli.list_occ_customer_groups, "list")
+
+
+# oci capacity-management occ-availability-catalog get-occ-availability-catalog-content -> oci capacity-management occ-availability-catalog get-catalog-content
+cli_util.rename_command(capacitymanagement_cli, capacitymanagement_cli.occ_availability_catalog_group, capacitymanagement_cli.get_occ_availability_catalog_content, "get-catalog-content")
+
+
+# oci capacity-management occ-availability-catalog-collection list-occ-availability-catalogs -> oci capacity-management occ-availability-catalog-collection list
+cli_util.rename_command(capacitymanagement_cli, capacitymanagement_cli.occ_availability_catalog_collection_group, capacitymanagement_cli.list_occ_availability_catalogs, "list")
+
+
+# oci capacity-management occ-availability-catalog-collection list-occ-availability-catalogs-internal -> oci capacity-management occ-availability-catalog-collection list-internal
+cli_util.rename_command(capacitymanagement_cli, capacitymanagement_cli.occ_availability_catalog_collection_group, capacitymanagement_cli.list_occ_availability_catalogs_internal, "list-internal")
+
+
+# oci capacity-management occ-availability-collection list-occ-availabilities -> oci capacity-management occ-availability-collection list
+cli_util.rename_command(capacitymanagement_cli, capacitymanagement_cli.occ_availability_collection_group, capacitymanagement_cli.list_occ_availabilities, "list")
+
+
+@cli_util.copy_params_from_generated_command(capacitymanagement_cli.create_occ_capacity_request, params_to_exclude=['region_parameterconflict'])
+@capacitymanagement_cli.occ_capacity_request_group.command(name=capacitymanagement_cli.create_occ_capacity_request.name, help=capacitymanagement_cli.create_occ_capacity_request.help)
+@cli_util.option('--target-region', required=True, help=u"""The name of the region for which the capacity request is made. [required]""")
+@click.pass_context
+@json_skeleton_utils.json_skeleton_generation_handler(input_params_to_complex_types={'freeform-tags': {'module': 'capacity_management', 'class': 'dict(str, string)'}, 'defined-tags': {'module': 'capacity_management', 'class': 'dict(str, dict(str, object))'}, 'details': {'module': 'capacity_management', 'class': 'list[OccCapacityRequestBaseDetails]'}}, output_type={'module': 'capacity_management', 'class': 'OccCapacityRequest'})
+@cli_util.wrap_exceptions
+def create_occ_capacity_request_extended(ctx, **kwargs):
+
+    if 'target_region' in kwargs:
+        kwargs['region_parameterconflict'] = kwargs['target_region']
+        kwargs.pop('target_region')
+
+    ctx.invoke(capacitymanagement_cli.create_occ_capacity_request, **kwargs)

services/capacity_management/src/oci_cli_capacity_management/generated/__init__.py

@@ -0,0 +1,4 @@
+# coding: utf-8
+# Copyright (c) 2016, 2024, Oracle and/or its affiliates.  All rights reserved.
+# This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license.
+# NOTE: This class is auto generated by OracleSDKGenerator. DO NOT EDIT. API Version: 20231107