Release 0.1.2

[isivaselvan]

Description

Feature

Registry Provider Version API Specs

https://developer.hashicorp.com/terraform/cloud-docs/api-docs/private-registry/provider-versions-platforms

Feature contains:

• list() --> Listing all versions
• create() --> Creating new registry provider version
• read() --> Show the specific registry provider version
• delete() --> Delete the specific registry provider version
• _registry_provider_version_from() --> Helper method to parse a version from API response data.
• Unit test cases added at tests/units/test_registry_provider_version.py
• examples added at examples/registry_provider_version.py
• Modified the utils.py to validate the string id pattern on whitespace and slashes.

QueryRuns

Following functions are created:

• list(workspace_id, options) - Lists all query runs for a workspace with automatic pagination
• create(options) - Creates a new query run with workspace and optional configuration version
• read(query_run_id) - Retrieves query run details by ID
• read_with_options(query_run_id, options) - Reads query run with relationship includes (created_by, configuration_version)
• logs(query_run_id) - Retrieves query run execution logs as an IO stream
• cancel(query_run_id, options) - Gracefully cancels a running query run with optional comment
• force_cancel(query_run_id, options) - Force cancels a stuck query run with optional comment

Refactoring

Refactored List method to return Iterator

Refactor involves, code modifications on list method and models of features at,

• Reserved Tag Key
• Oauth Token
• Policy Evaluation
• Policy Set Outcome
• Removed UID attribute at oauth token, as api docs doesn't have that key response.
• Removed Read method at Reserved Tag, as no such endpoint present in the api docs.
• Removed page number attribute from the List options model.

Testing plan

External links

Output from tests

Including output from tests may require access to a TFE instance. Ignore this section if you have no environment to test against.

Rollback Plan

Changes to Security Controls

PCI review checklist

• I have documented a clear reason for, and description of, the change I am making.

• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.

• If applicable, I've documented the impact of any changes to security controls.

  Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

If you have any questions, please contact your direct supervisor, GRC (#team-grc), or the PCI working group (#proj-pci-reboot). You can also find more information at PCI Compliance.