-
Notifications
You must be signed in to change notification settings - Fork 160
Expand file tree
/
Copy pathoutput.txt
More file actions
161 lines (105 loc) · 6.68 KB
/
output.txt
File metadata and controls
161 lines (105 loc) · 6.68 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
>>> DATABRICKS_BUNDLE_ENGINE=terraform [CLI] bundle plan
Recommendation: permissions section should explicitly include the current deployment identity '[USERNAME]' or one of its groups
If it is not included, CAN_MANAGE permissions are only applied if the present identity is used to deploy.
Consider using a adding a top-level permissions section such as the following:
permissions:
- user_name: [USERNAME]
level: CAN_MANAGE
See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
in databricks.yml:5:3
create pipelines.foo
create pipelines.foo.permissions
Plan: 2 to add, 0 to change, 0 to delete, 0 unchanged
>>> DATABRICKS_BUNDLE_ENGINE=terraform [CLI] bundle deploy
Recommendation: permissions section should explicitly include the current deployment identity '[USERNAME]' or one of its groups
If it is not included, CAN_MANAGE permissions are only applied if the present identity is used to deploy.
Consider using a adding a top-level permissions section such as the following:
permissions:
- user_name: [USERNAME]
level: CAN_MANAGE
See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
in databricks.yml:5:3
Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/dabs_revenue-[UNIQUE_NAME]/production/files...
Deploying resources...
Updating deployment state...
Deployment complete!
>>> print_requests.py //pipelines
>>> print_state.py
Recommendation: permissions section should explicitly include the current deployment identity '[USERNAME]' or one of its groups
If it is not included, CAN_MANAGE permissions are only applied if the present identity is used to deploy.
Consider using a adding a top-level permissions section such as the following:
permissions:
- user_name: [USERNAME]
level: CAN_MANAGE
See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
in databricks.yml:5:3
>>> [CLI] pipelines get [UUID]
>>> DATABRICKS_BUNDLE_ENGINE=terraform [CLI] bundle plan
Recommendation: permissions section should explicitly include the current deployment identity '[USERNAME]' or one of its groups
If it is not included, CAN_MANAGE permissions are only applied if the present identity is used to deploy.
Consider using a adding a top-level permissions section such as the following:
permissions:
- user_name: [USERNAME]
level: CAN_MANAGE
See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
in databricks.yml:5:3
Plan: 0 to add, 0 to change, 0 to delete, 2 unchanged
>>> DATABRICKS_BUNDLE_ENGINE= [CLI] bundle deployment migrate
Recommendation: permissions section should explicitly include the current deployment identity '[USERNAME]' or one of its groups
If it is not included, CAN_MANAGE permissions are only applied if the present identity is used to deploy.
Consider using a adding a top-level permissions section such as the following:
permissions:
- user_name: [USERNAME]
level: CAN_MANAGE
See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
in databricks.yml:5:3
Note: Migration should be done after a full deploy. Running plan now to verify that deployment was done:
Recommendation: permissions section should explicitly include the current deployment identity '[USERNAME]' or one of its groups
If it is not included, CAN_MANAGE permissions are only applied if the present identity is used to deploy.
Consider using a adding a top-level permissions section such as the following:
permissions:
- user_name: [USERNAME]
level: CAN_MANAGE
See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
in databricks.yml:5:3
Plan: 0 to add, 0 to change, 0 to delete, 2 unchanged
Success! Migrated 2 resources to direct engine state file: [TEST_TMP_DIR]/.databricks/bundle/production/resources.json
Validate the migration by running "databricks bundle plan", there should be no actions planned.
The state file is not synchronized to the workspace yet. To do that and finalize the migration, run "bundle deploy".
To undo the migration, remove [TEST_TMP_DIR]/.databricks/bundle/production/resources.json and rename [TEST_TMP_DIR]/.databricks/bundle/production/terraform/terraform.tfstate.backup to [TEST_TMP_DIR]/.databricks/bundle/production/terraform/terraform.tfstate
>>> print_state.py
>>> DATABRICKS_BUNDLE_ENGINE= [CLI] bundle plan
Recommendation: permissions section should explicitly include the current deployment identity '[USERNAME]' or one of its groups
If it is not included, CAN_MANAGE permissions are only applied if the present identity is used to deploy.
Consider using a adding a top-level permissions section such as the following:
permissions:
- user_name: [USERNAME]
level: CAN_MANAGE
See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
in databricks.yml:5:3
Plan: 0 to add, 0 to change, 0 to delete, 2 unchanged
>>> DATABRICKS_BUNDLE_ENGINE= [CLI] bundle plan -o json
Recommendation: permissions section should explicitly include the current deployment identity '[USERNAME]' or one of its groups
If it is not included, CAN_MANAGE permissions are only applied if the present identity is used to deploy.
Consider using a adding a top-level permissions section such as the following:
permissions:
- user_name: [USERNAME]
level: CAN_MANAGE
See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
in databricks.yml:5:3
>>> DATABRICKS_BUNDLE_ENGINE= [CLI] bundle destroy --auto-approve
Recommendation: permissions section should explicitly include the current deployment identity '[USERNAME]' or one of its groups
If it is not included, CAN_MANAGE permissions are only applied if the present identity is used to deploy.
Consider using a adding a top-level permissions section such as the following:
permissions:
- user_name: [USERNAME]
level: CAN_MANAGE
See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
in databricks.yml:5:3
The following resources will be deleted:
delete resources.pipelines.foo
This action will result in the deletion or recreation of the following Lakeflow Spark Declarative Pipelines along with the Streaming Tables (STs) and Materialized Views (MVs) managed by them:
delete resources.pipelines.foo
All files and directories at the following location will be deleted: /Workspace/Users/[USERNAME]/.bundle/dabs_revenue-[UNIQUE_NAME]/production
Deleting files...
Destroy complete!