From b66841f4ddee57f35269be7dbb5442b1742b63c9 Mon Sep 17 00:00:00 2001
From: omby8888 <160610297+omby8888@users.noreply.github.com>
Date: Mon, 30 Dec 2024 18:32:31 +0200
Subject: [PATCH] [Integration][PagerDuty] Port 12076 pagerduty OAuth support
 (#1276)

# Description

What -

Why -

How -

## Type of change

Please leave one option from the following and delete the rest:

- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] New Integration (non-breaking change which adds a new integration)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Non-breaking change (fix of existing functionality that will not
change current behavior)
- [ ] Documentation (added/updated documentation)

<h4> All tests should be run against the port production
environment(using a testing org). </h4>

### Core testing checklist

- [ ] Integration able to create all default resources from scratch
- [ ] Resync finishes successfully
- [ ] Resync able to create entities
- [ ] Resync able to update entities
- [ ] Resync able to detect and delete entities
- [ ] Scheduled resync able to abort existing resync and start a new one
- [ ] Tested with at least 2 integrations from scratch
- [ ] Tested with Kafka and Polling event listeners
- [ ] Tested deletion of entities that don't pass the selector


### Integration testing checklist

- [x] Integration able to create all default resources from scratch
- [x] Resync able to create entities
- [x] Resync able to update entities
- [x] Resync able to detect and delete entities
- [x] Resync finishes successfully
- [ ] If new resource kind is added or updated in the integration, add
example raw data, mapping and expected result to the `examples` folder
in the integration directory.
- [ ] If resource kind is updated, run the integration with the example
data and check if the expected result is achieved
- [ ] If new resource kind is added or updated, validate that
live-events for that resource are working as expected
- [ ] Docs PR link [here](#)

### Preflight checklist

- [ ] Handled rate limiting
- [ ] Handled pagination
- [ ] Implemented the code in async
- [ ] Support Multi account

## Screenshots

Include screenshots from your environment showing how the resources of
the integration will look.

## API Documentation

Provide links to the API documentation used for this integration.
---
 integrations/pagerduty/.port/spec.yaml | 2 +-
 integrations/pagerduty/CHANGELOG.md    | 5 +++++
 integrations/pagerduty/pyproject.toml  | 2 +-
 3 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/integrations/pagerduty/.port/spec.yaml b/integrations/pagerduty/.port/spec.yaml
index 7981143e7b..fba4b070ac 100644
--- a/integrations/pagerduty/.port/spec.yaml
+++ b/integrations/pagerduty/.port/spec.yaml
@@ -35,4 +35,4 @@ saas:
         description: '"Access Token for Pagerduty OAuth2 integration"'
     valuesOverride:
       integrationSpec:
-        appUrl: '"https://api.pagerduty.com"'
+        apiUrl: '"https://api.pagerduty.com"'
diff --git a/integrations/pagerduty/CHANGELOG.md b/integrations/pagerduty/CHANGELOG.md
index 8fe52c3a9c..1c1355bd0e 100644
--- a/integrations/pagerduty/CHANGELOG.md
+++ b/integrations/pagerduty/CHANGELOG.md
@@ -7,6 +7,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 <!-- towncrier release notes start -->
 
+## 0.2.1 (2024-12-30)
+
+- Fixed apiUrl typo in spec
+
+
 ## 0.2.0 (2024-12-30)
 
 
diff --git a/integrations/pagerduty/pyproject.toml b/integrations/pagerduty/pyproject.toml
index 2b06d0864b..a8e4c0d543 100644
--- a/integrations/pagerduty/pyproject.toml
+++ b/integrations/pagerduty/pyproject.toml
@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "pagerduty"
-version = "0.2.0"
+version = "0.2.1"
 description = "PagerDuty Integration"
 authors = ["Port Team <support@getport.io>"]