ORCA-4812: Document The dynamic_route_to action
#3
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
metavida
changed the title
dynamic_route_to actiondynamic_route_to action
metavida
commented
Jun 24, 2024
| @@ -12,15 +12,31 @@ An Orchestration Router allows users to create a set of Event Rules. The Router | |||
|
|
|||
| ## Example of configuring Router rules for an Orchestration | |||
|
|
|||
| In this example the user has defined the Router with two rules, each routing to a different service. | |||
|
|
|||
| This example assumes services used in the `route_to` configuration already exists. So it does not show creation of service resource. | |||
There was a problem hiding this comment.
Annotation: I decided it was easier to include a pair of service "data source" configurations in the example, rather having these disclaimer sentences.
metavida
commented
Jun 24, 2024
| @@ -72,6 +88,22 @@ The following arguments are supported: | |||
| * `expression`- (Required) A [PCL condition](https://developer.pagerduty.com/docs/ZG9jOjM1NTE0MDc0-pcl-overview) string. | |||
|
|
|||
| ### Actions (`actions`) supports the following: | |||
|
|
|||
| #### Dynamic Routing | |||
There was a problem hiding this comment.
Annotation: Unfortunately it seems the Terraform documentation site does not support deep links/anchors on H4 tags. That said I'm not immediately thinking of a better way to organize this portion of the page. Suggestions are welcome!
There was a problem hiding this comment.
I think the approach you chose is good, the Actions section is not that big so linking to Actions should be sufficient.
metavida
force-pushed
the
ORCA-4812-document-dynamic_route_to
branch
from
6f74385 to
dda518b
Compare
alenapan
approved these changes
Jun 25, 2024
alenapan
merged commit 0c0a56d
into
alenapan:event-orchestration-dynamic-routing-and-esc-policy-support
alenapan
pushed a commit
that referenced
this pull request
Jul 12, 2024
Migrate pack #3 of datasources and resources to terraform plugin framework
c-kaieong
pushed a commit
that referenced
this pull request
Jul 22, 2024
* Update the router example to use the pagerduty_service data source * Add a dynamic router rule example * Document the dynamic vs static router actions
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.
Adds documentation for the
dynamic_route_toaction. The wording is based partially on the proposed public-REST-API wording in ORCA-4803.QA
I pasted the markdown into https://registry.terraform.io/tools/doc-preview and got this result: