Tags: VestedInsight/fides
Tags
1.7.0 Release PR (ethyca#797) Co-authored-by: Sebastian Sangervasi <[email protected]>
Update CHANGELOG.md (ethyca#536) * Update CHANGELOG.md * Update CHANGELOG.md * Update CHANGELOG.md * Update CHANGELOG.md
Bump fideslog to v1.1.3, update usage patterns (ethyca#453) * Update the usage of `AnalyticsClient.send`, bump fideslog to v1.1.0 Fideslog v1.1.0 changes the `AnalyticsClient.send` interface such that it automatically executes the request in a separate event loop. There is no longer a need to manually wrap the call in `asyncio.run` or similar. These changes were introduced in ethyca/fideslog#50 * Use the new `OPT_OUT_PROMPT` constant * `AnalyticsException` --> `AnalyticsError` * Bump fideslog to v1.1.1 * Bump fideslog to v1.1.2 * Bump fideslog to v1.1.3
Clarify log output from `fidesctl status` (ethyca#480) * Log success message only when successful * Don't check status when running status * Use a more straightforward conditional
move init to LOCAL_COMMANDS (ethyca#476) * move init to LOCAL_COMMANDS This was discovered while resolving the missing commands for a pip installation. It appears that the server/cli check was running when trying to use the init command. This caused an error to be returned when using the quickstart. I'd also like to do some further testing against fidesdemo. * add the init to connectors Co-authored-by: ThomasLaPiana <[email protected]>
Guide for Exporting a Data Map / RoPA (ethyca#449) * data map user guide This is a first draft of what a user guide might look like. Some further details are still necessary, but I wanted to explore the style of using the demo_resources and extending them appropriately to get to a data map. Separately, it might make more sense to either tack this on to the flask app walkthrough, create a separate walkthrough, or simplify this by reorganizaing in a meaningful way. * fix type in default taxonomy for Customer * consolidate extended taxonomy to one manifest * additional information for extending the taxonomy * small word fixes * refactor datamap generation docs * analytics rm * word fixes * minor words and trailing spaces Co-authored-by: ThomasLaPiana <[email protected]> Co-authored-by: Cole Isaac <[email protected]>
Don't create an `AnalyticsClient` if it won't be used (ethyca#419) When running `fidesctl init`, the `AnalyticsClient` does not need to be created; analytics are not sent for running `fidesctl init`. In the worst case, attempting to create an `AnalyticsClient` will raise an exception if the user does not already have an `analytics_id` written to their config file.
Send "developer" analytics events in test mode (ethyca#405) * Send "developer" analytics when appropriate * Allow for a local `FIDESCTL__CLI__ANALYTICS_ID` env variable override If set in a user's local ENV, the value of `FIDESCTL__CLI__ANALYTICS_ID` will be used to populate the `analytics_id` config value when executing Makefile targets. * Don't allow an `analytics_id` of "" * Explicitly resolve `developer_mode` to a bool * Use `FIDESCTL__CLI__ANALYTICS_ID` directly
Integrate fideslog for anonymous CLI analytics (ethyca#386) * Populate IDs and opt out vars with fides init * updates for fidesctl init, add git url to reqs * [skip ci] sample event tracking * move event tracking to groups * finish opt out routeine for non-init commands * remove api key requirement, add initial tracking as middleware * Remove analytics IDs from pushed TOML * Remove unversioned fideslog import * Move `update_config_file` helper to `core` package * Rework the cold-start opt-out routine For users who have not run `fidesctl init`, nor made a decision about opting out of analytics data collection, prompt them for a decision and write the results to `fidesctl.toml`. * minor adjustments to facilitate opt-out improvements, fix incorrect port left from earlier commit * updates for fideslog sdk v0.9.1 * remove fideslog usage from fidesapi * Remove remaining API-related analytics code * Store the analytics client in command context * minor updates to setting analytics_client, trying different areas for capturing commands * Store the `AnalyticsClient` in the meta context Also uses the internally-defined product name, vs. a new constant * Wrap CLI command execution in a `with_analytics` helper The `with_analytics` wrapper function captures metadata about the executed command before/during/after execution, and optionally sends an `AnalyticsEvent` to the fideslog server based on user configuration. * Don't send analytics during testing * Simplify `with_analytics` helper * Add analytics to remaining CLI commands * Opt out of analytics * Check installation and evaluation using the test config file * Include real values in every `AnalyticsEvent` * Require an explicit opt-in for analytics Theoretically, the user should never have an opportunity to run a command without making an opt-in or opt-out decision. This change simply codifies the intent to require opt-in vs. opt-out. * Treat `fidesctl init` like a special case * Opt-out analytics when testing `fidesctl init` * document configuration changes, init command, and opt-out routine messaging * Apply suggestions from code review Co-authored-by: Phil Salant <[email protected]> * Create the get_config_path helper * bump fideslog to 1.0.0 * use a more programmatic event name * ensure fideslog fails silently * comment on why init is handled separately * testing for update_config_file * Send the name of the error type in event details * Print the config path when updating config files * Independently update `analytics_opt_out` and `analytics_id` The presence of an `analytics_id` in the config file needs to be checked explicitly. If a user manually adds `analytics_opt_out = false`, their `analytics_id` is never added to the config file. This results in an opted-in user, who continuously pushes events to fideslog with a newly generated `analytics_id` value. * Appease the almighty xenon Co-authored-by: Phil Salant <[email protected]> Co-authored-by: Phil Salant <[email protected]>
PreviousNext