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

CFE-4442: Clarified need to specify namespace when defining custom policy update bundle #2948

Merged
merged 2 commits into from
Oct 10, 2024

Conversation

nickanderson
Copy link
Member

This change clarifies the need to specify the namespace when defining a custom policy update bundle both in documentation in reports emitted by policy.

If namespace is not specified the bundle will not be found and will be unable to run.

@nickanderson
Copy link
Member Author

@craigcomstock could you take this for a spin?

Also, the Warning message that I added, it's currently classed to inform_mode|verbose_mode|DEBUG|DEBUG_cfe_internal_update_policy:: Do you think that's OK, or do you think that it should be emitted in any context?

"User specified update bundle: $(def.mpf_update_policy_bundle)"
if => "have_user_specified_update_bundle";

"WARNING User specified update bundle '$(def.mpf_update_policy_bundle)' does not specify a namespace. Please specify a namespace, e.g. 'default:$(def.mpf_update_policy_bundle)'."
Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, I think this should be moved outside of the current guards and made to report at any running log level, e.g. any::

@nickanderson nickanderson merged commit 5f5523e into cfengine:master Oct 10, 2024
4 checks passed
@nickanderson nickanderson added the cherry-pick? Fixes which may need to be cherry-picked to LTS branches label Oct 10, 2024
@nickanderson
Copy link
Member Author

Yes, this should be picked to 3.24.x and 3.21.x. I have yet to do it.

@nickanderson nickanderson removed the cherry-pick? Fixes which may need to be cherry-picked to LTS branches label Oct 10, 2024
@nickanderson
Copy link
Member Author

backported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants