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
Currently, when attempting to use the same dataset name across different integrations, such as Custom Logs and Custom HTTP Endpoint Logs, the creation of these integration policies is not permitted. An error message is displayed:
Index template "<template-name>" already exist and is not managed by this package, force flag is required
The current workaround involves using the force option, but there is a lack of clarity regarding the safety and implications of this option.
It would be beneficial to provide documentation detailing the process and safety considerations for using the force flag. And maybe implementing a user interface option to apply the force option with a clear confirmation prompt.
The text was updated successfully, but these errors were encountered:
Currently, when attempting to use the same dataset name across different integrations, such as Custom Logs and Custom HTTP Endpoint Logs, the creation of these integration policies is not permitted. An error message is displayed:
The current workaround involves using the force option, but there is a lack of clarity regarding the safety and implications of this option.
It would be beneficial to provide documentation detailing the process and safety considerations for using the force flag. And maybe implementing a user interface option to apply the force option with a clear confirmation prompt.
The text was updated successfully, but these errors were encountered: