release: 0.15.0 #128
Merged
release: 0.15.0 #128
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Tiago Barbosa <[email protected]>
Signed-off-by: Tiago Barbosa <[email protected]>
Signed-off-by: Tiago Barbosa <[email protected]>
…as settings Signed-off-by: Tiago Barbosa <[email protected]>
Signed-off-by: Tiago Barbosa <[email protected]>
### Description This PR updates the `PagerDutyPage` component to add a new configurations tab where users can configure how they want to sync service dependencies between Backstage and PagerDuty.  **By default, service dependency syncing is disabled.** It's an opt-in feature and admins need to be aware of what it does because you might end up deleting existing service dependencies on Backstage or PagerDuty. **Issue number:** N/A ### Type of change - [x] New feature (non-breaking change which adds functionality) - [ ] Fix (non-breaking change which fixes an issue) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) ### Checklist - [x] I have performed a self-review of this change - [x] Changes have been tested - [ ] Changes are documented - [x] Changes generate *no new warnings* - [x] PR title follows [conventional commit semantics](https://www.conventionalcommits.org/en/v1.0.0/) If this is a breaking change 👇 - [ ] I have documented the migration process - [ ] I have implemented necessary warnings (if it can live side by side) ## Acknowledgement By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice. **Disclaimer:** We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.
Signed-off-by: Tiago Barbosa <[email protected]>
### Description This PR introduces a fix to the issue reported on #123 that prevents users from showing/hiding columns in the service mapping table on `PagerDutyPage`. **Issue number:** #123 ### Type of change - [ ] New feature (non-breaking change which adds functionality) - [x] Fix (non-breaking change which fixes an issue) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) ### Checklist - [x] I have performed a self-review of this change - [x] Changes have been tested - [ ] Changes are documented - [x] Changes generate *no new warnings* - [x] PR title follows [conventional commit semantics](https://www.conventionalcommits.org/en/v1.0.0/) If this is a breaking change 👇 - [ ] I have documented the migration process - [ ] I have implemented necessary warnings (if it can live side by side) ## Acknowledgement By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice. **Disclaimer:** We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.
…limitation on Backstage Signed-off-by: Tiago Barbosa <[email protected]>
…kstage (#127) ### Description This PR disables PagerDuty option on service dependency syncing configuration in `PagerDutyPage`. There is a design option on Backstage that prevents us to fully replace or remove existing relations from an entity configuration file. For that reason we are not able to guarantee that proper behaviour of PagerDuty syncing to Backstage. Users can still choose to have Backstage as a main source, ou to use both Backstage and PagerDuty which will merge the two sets of service dependencies in both platforms and keep them in sync. **Issue number:** N/A ### Type of change - [ ] New feature (non-breaking change which adds functionality) - [x] Fix (non-breaking change which fixes an issue) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) ### Checklist - [x] I have performed a self-review of this change - [x] Changes have been tested - [ ] Changes are documented - [x] Changes generate *no new warnings* - [x] PR title follows [conventional commit semantics](https://www.conventionalcommits.org/en/v1.0.0/) If this is a breaking change 👇 - [ ] I have documented the migration process - [ ] I have implemented necessary warnings (if it can live side by side) ## Acknowledgement By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice. **Disclaimer:** We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This release updates the
PagerDutyPagecomponent to add a new configurations tab where users can configure how they want to sync service dependencies between Backstage and PagerDuty.By default, service dependency syncing is disabled. It's an opt-in feature and admins need to be aware of what it does because you might end up deleting existing service dependencies on Backstage or PagerDuty.
On this release we also introduced a fix that was preventing users from showing/hiding columns on the service to entity mapping table (#123).
Acknowledgement
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.