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

Fixed #400 - unset not working for systemuser #413

Merged
merged 5 commits into from
Apr 17, 2024

Conversation

sumanth-lingappa
Copy link
Collaborator

In NITRO documentation, the attributes type is str, int, list etc. But these attributes when present in "unset" operation, their type changes to bool.
Hence for all the attributes present in "unset" action, their type is changed to "raw" so that ansible should not throw error for type-mismatch

@sumanth-lingappa sumanth-lingappa linked an issue Apr 15, 2024 that may be closed by this pull request
Copy link

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request

@sumanth-lingappa sumanth-lingappa merged commit b4de90d into main Apr 17, 2024
11 of 12 checks passed
@sumanth-lingappa sumanth-lingappa deleted the 400-bug-systemuser-unset-not-working branch April 17, 2024 04:11
@github-actions github-actions bot locked and limited conversation to collaborators Apr 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Systemuser "unset" not working
1 participant