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

feat!: Make callbacks and public_key attributes public #5

Merged
merged 3 commits into from
Feb 5, 2024

Conversation

NucciTheBoss
Copy link
Member

Decided to make the callback and public_key attributes "public" since I need them in the Slurm snap for processing configuration values that come in via the command line. Now linters will not complain about developers accessing the callbacks for performing additional parsing and marshalling when configuration changes come in from a different location that is not a Slurm-related configuration file.

BREAKING CHANGES: Removes the leading underscore from the callbacks and private_key attribute. This will break anyone accessing these attributes to perform operations on Slurm configuration data.

Making these attributes public enables developers to use the callbacks for parsing configuration values that do not come in through a configuration file. REST API, command line, etc.

BREAKING CHANGE: These attributes are no longer protected (have the prepended underscore). Any method relying on the protected attributes will now fail since the variables are now public.

Signed-off-by: Jason C. Nucciarone <[email protected]>
@NucciTheBoss NucciTheBoss added Priority: Medium This should be addressed by the end of the sprint. Type: Refactor Proposes changes to the code base but does not fundamentally change the API. labels Feb 5, 2024
@NucciTheBoss NucciTheBoss self-assigned this Feb 5, 2024
Signed-off-by: Jason C. Nucciarone <[email protected]>
@NucciTheBoss NucciTheBoss merged commit 2770c1a into main Feb 5, 2024
4 checks passed
@NucciTheBoss NucciTheBoss deleted the public-callbacks branch February 5, 2024 23:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Medium This should be addressed by the end of the sprint. Type: Refactor Proposes changes to the code base but does not fundamentally change the API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant