You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CSPL-3499: Fix Segmentation Fault in Splunk Operator Due to App Volume Name Change (#1468)
* handle error from remoteDataClientMgr
* implement unit test for bug fix
* add comment in documentation
* update comment on test case
* udpate error log to be easier to debug
Copy file name to clipboardExpand all lines: docs/AppFramework.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -577,6 +577,8 @@ Here is a typical App framework configuration in a Custom Resource definition:
577
577
578
578
`appSources`defines the name and scope of the appSource, the remote storage volume, and its location.
579
579
580
+
NOTE: If an app source name needs to be changed, make sure the name change is persisted across the app framework spec and CR status. The Splunk Operator should automatically update the app path in the CR and on the pod on the next reconciliation.
581
+
580
582
* `name` uniquely identifies the App source configuration within a CR. This used locally by the Operator to identify the App source.
581
583
* `scope` defines the scope of the app to be installed.
582
584
* If the scope is `local`, the apps will be installed and run locally on the pod referred to by the CR.
0 commit comments