Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENT-9531: Added reports for enterprise users to migrate db retention settings #2525

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

nickanderson
Copy link
Member

@nickanderson nickanderson commented Oct 24, 2022

This change is intended to ensure that customizations users have made related to
data retention are migrated to the new location where cf-reactor can make use of them.

Example output when retention settings have been modified:

R: NOTICE: 'default:cfe_internal_hub_maintain.report_settings' has been customized. These settings have moved to Mission Portal as cf-reactor has taken over responsibility for maintaining this data.
R: NOTICE: contexts history_length_days has been customized. Default: 7 Set: 71
R: NOTICE: 'default:cfe_internal_hub_maintain.diagnostics_settings' has been customized. These settings have moved to Mission Portal as cf-reactor has taken over responsibility for maintaining this data.
R: NOTICE: diagnostics history_length_days has been customized. Default: 1 Set: 21

Ticket: ENT-9531
Changelog: Title

This change is intended to ensure that customizations users have made related to
data retention are migrated to the new location where cf-reactor can make use of them.

Ticket: ENT-9531
Changelog: Title
{
classes:
"running_binary_with_new_db_retention_settings"
expression => "cfengine_3_22_0|feature_cf_reactor_report_retention";
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was just a WAG for the context. Ideally, we will have a non version based class to key off of for this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, maybe a feature class? Or something similar.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeahp, I like the thought of a feature class.

@nickanderson nickanderson added the WIP Work in Progress label Oct 24, 2022
@nickanderson
Copy link
Member Author

Tagged WIP because this doesn't need to be prioritized for release and it may change based on other implementation details no yet determined.

Copy link
Contributor

@vpodzime vpodzime left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK. We will see how things evolve before this is needed.

@nickanderson nickanderson added onhold Ticket placed on hold until developers have time to resume work after-release labels Oct 25, 2022
Copy link
Member

@olehermanse olehermanse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 , but don't merge until needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
onhold Ticket placed on hold until developers have time to resume work WIP Work in Progress
3 participants