Skip to content
This repository has been archived by the owner on Jun 2, 2024. It is now read-only.

Migrate Custom Event Specifications into single resource #170

Closed
gessnerfl opened this issue Sep 1, 2023 · 2 comments
Closed

Migrate Custom Event Specifications into single resource #170

gessnerfl opened this issue Sep 1, 2023 · 2 comments
Assignees
@gessnerfl
Labels
feature New feature or request
Milestone
1.8.0

Comments

@gessnerfl
Copy link
Owner

gessnerfl commented Sep 1, 2023 •
edited
Loading

Currently we maintain different resources for the different types of custom event specifications.
Scope of this story is to migrate them into a single resource with sub schemas. This makes the provider leaner and fit to the API

This will be a breaking change and users will need to update the configuration.
@gessnerfl gessnerfl added feature New feature or request breaking A breaking change to the terraform provider labels Sep 1, 2023
@gessnerfl gessnerfl added this to the 2.0.0 milestone Sep 1, 2023
@gessnerfl gessnerfl self-assigned this Sep 1, 2023
@gessnerfl gessnerfl changed the title Migrate Alerting Channels into single resource Migrate Custom Event Specifications into single resource Sep 1, 2023
@gessnerfl gessnerfl added improvement An internal improvement/refactoring and removed feature New feature or request labels Sep 1, 2023
gessnerfl pushed a commit that referenced this issue Sep 3, 2023
#170: create docu and first schema draft
ba975f0
@gessnerfl
Copy link
Owner Author

The change must be implemented such as, that new resource must be provided first in a new 1.8.0 release side by side to the. existing resources. This will allow users to migrate the resources properly. Otherwise the resource type will be unknown so that users will not even be able to destroy the existing custom event specifications.

gessnerfl added a commit that referenced this issue Sep 4, 2023
@gessnerfl
#170: add custom-event-specification resource
d574a7c
@gessnerfl gessnerfl modified the milestones: 2.0.0, 1.8.0 Sep 6, 2023
@gessnerfl gessnerfl mentioned this issue Sep 6, 2023
Closed
@gessnerfl gessnerfl added feature New feature or request and removed breaking A breaking change to the terraform provider improvement An internal improvement/refactoring labels Sep 6, 2023
@gessnerfl
Copy link
Owner Author

The rule specific resources must be marked as deprecated.

gessnerfl added a commit that referenced this issue Sep 6, 2023
@gessnerfl
#170: implement unit tests for custom-event-specification resource
c541e33
gessnerfl added a commit that referenced this issue Sep 7, 2023
@gessnerfl
#170: implement integration tests for custom-event-specification reso…
0c0fd6b 
…urce and integrate into provider
gessnerfl added a commit that referenced this issue Sep 7, 2023
@gessnerfl
#170: update documentation and mark rule specific resources as deprec…
1e5193b 
…ated
gessnerfl added a commit that referenced this issue Sep 7, 2023
@gessnerfl
#170: fix typo
54f67ed
gessnerfl added a commit that referenced this issue Sep 7, 2023
@gessnerfl
#170: fix code quality issues
5fd7fe0
gessnerfl added a commit that referenced this issue Sep 7, 2023
@gessnerfl
Merge pull request #179 from gessnerfl/feature/170_custom_event_spec
5f887ad 
closes #170: new resource added combining all existing custom event specification rule type. Old resources marked as deprecated. Q-metrics ok. Manual and automated tests executed successfully.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@gessnerfl gessnerfl

Labels
feature New feature or request
Projects
None yet
Milestone
1.8.0
Development

No branches or pull requests
1 participant
@gessnerfl