@pulumi/newrelic 5.80.0 → 5.80.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +2 -2
- package/team.d.ts +3 -3
- package/team.js +3 -3
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@pulumi/newrelic",
|
|
3
|
-
"version": "5.80.
|
|
3
|
+
"version": "5.80.1",
|
|
4
4
|
"description": "A Pulumi package for creating and managing New Relic resources.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pulumi",
|
|
@@ -23,6 +23,6 @@
|
|
|
23
23
|
"pulumi": {
|
|
24
24
|
"resource": true,
|
|
25
25
|
"name": "newrelic",
|
|
26
|
-
"version": "5.80.
|
|
26
|
+
"version": "5.80.1"
|
|
27
27
|
}
|
|
28
28
|
}
|
package/team.d.ts
CHANGED
|
@@ -6,7 +6,7 @@ import * as outputs from "./types/output";
|
|
|
6
6
|
*
|
|
7
7
|
* Teams group people and associate owned entities (services, dashboards, scorecards, and more) under a single operational identity. They appear across alerts, service maps, and the Teams UI.
|
|
8
8
|
*
|
|
9
|
-
* > **NOTE:** Entity ownership is managed non-authoritatively. Terraform tracks only the entities you declare in the `entities` block and ensures they remain in the collection. Entities added to the collection outside Terraform — through tag-based discovery
|
|
9
|
+
* > **NOTE:** Entity ownership is managed non-authoritatively. Terraform tracks only the entities you declare in the `entities` block and ensures they remain in the collection. Entities added to the collection outside Terraform — through tag-based discovery or manual additions via the UI or API — are not surfaced as drift and are not removed on apply. To disable entity management entirely and suppress all entity-related plan output, set `entityManagementMode = "unmanaged"`.
|
|
10
10
|
*
|
|
11
11
|
* ## Example Usage
|
|
12
12
|
*
|
|
@@ -64,7 +64,7 @@ import * as outputs from "./types/output";
|
|
|
64
64
|
*
|
|
65
65
|
* Terraform manages a declared set of entities within the team's ownership collection using a non-authoritative approach. You declare which entity GUIDs Terraform should track; Terraform ensures those entities are present in the collection and surfaces a plan change only when one of them is missing.
|
|
66
66
|
*
|
|
67
|
-
* Entities added to the collection outside Terraform — through tag-based discovery
|
|
67
|
+
* Entities added to the collection outside Terraform — through tag-based discovery or manual additions via the UI or API — are not surfaced as drift and are not removed on apply. This means the ownership collection can contain more entities than are declared in `entities`, and Terraform will not interfere with those additional entries.
|
|
68
68
|
*
|
|
69
69
|
* **When to use:** You want Terraform to maintain a specific set of owned entities (for example, a scorecard or a key service) while allowing the platform to populate the rest of the collection through its own discovery mechanisms.
|
|
70
70
|
*
|
|
@@ -90,7 +90,7 @@ import * as outputs from "./types/output";
|
|
|
90
90
|
*
|
|
91
91
|
* ### `unmanaged`
|
|
92
92
|
*
|
|
93
|
-
* Terraform does not manage the team's entity ownership collection at all. The collection is left entirely to the New Relic platform — tag-based discovery
|
|
93
|
+
* Terraform does not manage the team's entity ownership collection at all. The collection is left entirely to the New Relic platform — tag-based discovery or manual management through the Teams UI or API.
|
|
94
94
|
*
|
|
95
95
|
* **When to use:** Entity ownership for this team is governed entirely outside Terraform (for example, by tagging conventions). You want to manage the team resource itself — name, aliases, members — without Terraform interfering with what the platform assigns to the collection.
|
|
96
96
|
*
|
package/team.js
CHANGED
|
@@ -33,7 +33,7 @@ const utilities = __importStar(require("./utilities"));
|
|
|
33
33
|
*
|
|
34
34
|
* Teams group people and associate owned entities (services, dashboards, scorecards, and more) under a single operational identity. They appear across alerts, service maps, and the Teams UI.
|
|
35
35
|
*
|
|
36
|
-
* > **NOTE:** Entity ownership is managed non-authoritatively. Terraform tracks only the entities you declare in the `entities` block and ensures they remain in the collection. Entities added to the collection outside Terraform — through tag-based discovery
|
|
36
|
+
* > **NOTE:** Entity ownership is managed non-authoritatively. Terraform tracks only the entities you declare in the `entities` block and ensures they remain in the collection. Entities added to the collection outside Terraform — through tag-based discovery or manual additions via the UI or API — are not surfaced as drift and are not removed on apply. To disable entity management entirely and suppress all entity-related plan output, set `entityManagementMode = "unmanaged"`.
|
|
37
37
|
*
|
|
38
38
|
* ## Example Usage
|
|
39
39
|
*
|
|
@@ -91,7 +91,7 @@ const utilities = __importStar(require("./utilities"));
|
|
|
91
91
|
*
|
|
92
92
|
* Terraform manages a declared set of entities within the team's ownership collection using a non-authoritative approach. You declare which entity GUIDs Terraform should track; Terraform ensures those entities are present in the collection and surfaces a plan change only when one of them is missing.
|
|
93
93
|
*
|
|
94
|
-
* Entities added to the collection outside Terraform — through tag-based discovery
|
|
94
|
+
* Entities added to the collection outside Terraform — through tag-based discovery or manual additions via the UI or API — are not surfaced as drift and are not removed on apply. This means the ownership collection can contain more entities than are declared in `entities`, and Terraform will not interfere with those additional entries.
|
|
95
95
|
*
|
|
96
96
|
* **When to use:** You want Terraform to maintain a specific set of owned entities (for example, a scorecard or a key service) while allowing the platform to populate the rest of the collection through its own discovery mechanisms.
|
|
97
97
|
*
|
|
@@ -117,7 +117,7 @@ const utilities = __importStar(require("./utilities"));
|
|
|
117
117
|
*
|
|
118
118
|
* ### `unmanaged`
|
|
119
119
|
*
|
|
120
|
-
* Terraform does not manage the team's entity ownership collection at all. The collection is left entirely to the New Relic platform — tag-based discovery
|
|
120
|
+
* Terraform does not manage the team's entity ownership collection at all. The collection is left entirely to the New Relic platform — tag-based discovery or manual management through the Teams UI or API.
|
|
121
121
|
*
|
|
122
122
|
* **When to use:** Entity ownership for this team is governed entirely outside Terraform (for example, by tagging conventions). You want to manage the team resource itself — name, aliases, members — without Terraform interfering with what the platform assigns to the collection.
|
|
123
123
|
*
|