Skip to content

Commit

Permalink
Cut Release 'v1.3.2'
Browse files Browse the repository at this point in the history
  • Loading branch information
opslevel-ops committed Oct 28, 2024
1 parent 23295a0 commit 8d85968
Show file tree
Hide file tree
Showing 11 changed files with 404 additions and 20 deletions.
3 changes: 0 additions & 3 deletions .changes/unreleased/Bugfix-20241022-094434.yaml

This file was deleted.

3 changes: 0 additions & 3 deletions .changes/unreleased/Dependency-20241016-084347.yaml

This file was deleted.

3 changes: 0 additions & 3 deletions .changes/unreleased/Dependency-20241021-013021.yaml

This file was deleted.

3 changes: 0 additions & 3 deletions .changes/unreleased/Feature-20241004-155834.yaml

This file was deleted.

4 changes: 0 additions & 4 deletions .changes/unreleased/Feature-20241022-094830.yaml

This file was deleted.

3 changes: 0 additions & 3 deletions .changes/unreleased/Feature-20241022-161548.yaml

This file was deleted.

10 changes: 10 additions & 0 deletions .changes/v1.3.2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
## [October 28, 2024](https://github.com/OpsLevel/terraform-provider-opslevel/compare/v1.3.1...v1.3.2)
### Bugfix
- correctly update missing_package_result field in opslevel_check_package_version
### Feature
- add opslevel_integration_endpoint resource to create and update integration endpoints
- Add `opslevel_alias` resource for managing a set of aliases on an "aliasable" resource in OpsLevel
- Add new resource to manage Code Issue Checks - 'opslevel_check_code_issue'
### Dependency
- bump github.com/hashicorp/terraform-plugin-framework version to v1.12.0
- Bump github.com/hashicorp/terraform-plugin-framework-validators from 0.13.0 to 0.14.0
11 changes: 10 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,16 @@
All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and is generated by [Changie](https://github.com/miniscruff/changie).## [October 15, 2024](https://github.com/OpsLevel/terraform-provider-opslevel/compare/v1.3.0...v1.3.1)
and is generated by [Changie](https://github.com/miniscruff/changie).## [October 28, 2024](https://github.com/OpsLevel/terraform-provider-opslevel/compare/v1.3.1...v1.3.2)
### Bugfix
- correctly update missing_package_result field in opslevel_check_package_version
### Feature
- add opslevel_integration_endpoint resource to create and update integration endpoints
- Add `opslevel_alias` resource for managing a set of aliases on an "aliasable" resource in OpsLevel
- Add new resource to manage Code Issue Checks - 'opslevel_check_code_issue'
### Dependency
- bump github.com/hashicorp/terraform-plugin-framework version to v1.12.0
- Bump github.com/hashicorp/terraform-plugin-framework-validators from 0.13.0 to 0.14.0## [October 15, 2024](https://github.com/OpsLevel/terraform-provider-opslevel/compare/v1.3.0...v1.3.1)
### Bugfix
- fix predicate validation to accept interpolated values on value field
- TF state correctly detects service owner changes from UI
Expand Down
72 changes: 72 additions & 0 deletions docs/resources/alias.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,72 @@
---
# generated by https://github.com/hashicorp/terraform-plugin-docs
page_title: "opslevel_alias Resource - terraform-provider-opslevel"
subcategory: ""
description: |-
Alias Resource
---

# opslevel_alias (Resource)

Alias Resource

## Example Usage

```terraform
resource "opslevel_alias" "service" {
resource_type = "service"
resource_identifier = "example_alias"
aliases = ["example_alias_2", "example_alias_3"]
}
resource "opslevel_alias" "team" {
resource_type = "team"
resource_identifier = "example_alias"
aliases = ["example_alias_2", "example_alias_3"]
}
resource "opslevel_alias" "domain" {
resource_type = "domain"
resource_identifier = "example_alias"
aliases = ["example_alias_2", "example_alias_3"]
}
resource "opslevel_alias" "system" {
resource_type = "system"
resource_identifier = "example_alias"
aliases = ["example_alias_2", "example_alias_3"]
}
resource "opslevel_alias" "infra" {
resource_type = "infrastructure_resource"
resource_identifier = "example_alias"
aliases = ["example_alias_2", "example_alias_3"]
}
resource "opslevel_alias" "scorecard" {
resource_type = "scorecard"
resource_identifier = "example_alias"
aliases = ["example_alias_2", "example_alias_3"]
}
```

<!-- schema generated by tfplugindocs -->
## Schema

### Required

- `aliases` (Set of String) The unique set of aliases to ensure exist on the resource.
- `resource_identifier` (String) The id or human-friendly, unique identifier of the resource this alias belongs to.
- `resource_type` (String) The resource type that the alias applies to. One of `service`, `team`, `group`, `system`, `domain`, `infrastructure_resource`, `scorecard`

### Read-Only

- `id` (String) The id of the resource, maybe be duplicative of the 'resource_identifier' but in the case where that is an alias itself this is the identifier of what it found during lookup.


121 changes: 121 additions & 0 deletions docs/resources/check_code_issue.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,121 @@
---
# generated by https://github.com/hashicorp/terraform-plugin-docs
page_title: "opslevel_check_code_issue Resource - terraform-provider-opslevel"
subcategory: ""
description: |-
Check Code Issue Resource
---

# opslevel_check_code_issue (Resource)

Check Code Issue Resource

## Example Usage

```terraform
data "opslevel_rubric_category" "security" {
filter {
field = "name"
value = "Security"
}
}
data "opslevel_rubric_level" "bronze" {
filter {
field = "name"
value = "Bronze"
}
}
data "opslevel_team" "devs" {
alias = "developers"
}
data "opslevel_filter" "tier1" {
filter {
field = "name"
value = "Tier 1"
}
}
resource "opslevel_check_code_issue" "example" {
name = "foo"
pass_pending = true
enabled = true
# To set a future enable date remove field 'enabled' and use 'enable_on'
# enable_on = "2022-05-23T14:14:18.782000Z"
category = data.opslevel_rubric_category.security.id
level = data.opslevel_rubric_level.bronze.id
owner = data.opslevel_team.devs.id
filter = data.opslevel_filter.tier1.id
notes = "Optional additional info on why this check is run or how to fix it"
constraint = "any"
issue_name = "CVE-2024-0001"
issue_type = [
"snyk:code",
"snyk:cloud",
"snyk:config",
"snyk:custom",
"snyk:license",
"snyk:package_vulnerability",
]
max_allowed = 5
resolution_time = {
unit = "day"
value = 3
}
severity = [
"snyk:critical",
"snyk:low",
"snyk:medium",
"snyk:high",
]
}
```

<!-- schema generated by tfplugindocs -->
## Schema

### Required

- `category` (String) The id of the category the check belongs to.
- `constraint` (String) The type of constraint used in evaluation the code issues check.
- `level` (String) The id of the level the check belongs to.
- `name` (String) The display name of the check.

### Optional

- `enable_on` (String) The date when the check will be automatically enabled.
If you use this field you should add both 'enabled' and 'enable_on' to the lifecycle ignore_changes settings.
See example in opslevel_check_manual for proper configuration.
- `enabled` (Boolean) Whether the check is enabled or not. Do not use this field in tandem with 'enable_on'.
- `filter` (String) The id of the filter of the check.
- `issue_name` (String) The issue name used for code issue lookup.
- `issue_type` (List of String) The types of code issues to consider.
- `max_allowed` (Number) The threshold count of code issues beyond which the check starts failing.
- `notes` (String) Additional information to display to the service owner about the check.
- `owner` (String) The id of the team that owns the check.
- `resolution_time` (Attributes) Defines the minimum frequency of the updates. (see [below for nested schema](#nestedatt--resolution_time))
- `severity` (List of String) The severity levels of the issue.

### Read-Only

- `description` (String) The description the check.
- `id` (String) The id of the check.

<a id="nestedatt--resolution_time"></a>
### Nested Schema for `resolution_time`

Required:

- `unit` (String) The name of duration of time.
- `value` (Number) The count value of the specified unit.

## Import

Import is supported using the following syntax:

```shell
terraform import opslevel_check_code_issue.example Z2lkOi8vb3BzbGV2ZWwvU2VydmljZS82MDI0
```
Loading

0 comments on commit 8d85968

Please sign in to comment.