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

Issue #322 #338

Merged
merged 7 commits into from
Jan 11, 2024
Merged

Issue #322 #338

merged 7 commits into from
Jan 11, 2024

Conversation

sumanth-lingappa
Copy link
Collaborator

No description provided.

`ntpserver` can have two possible primary_keys - `serverip` and `servername`. however in the NITRO schema, only serverip is defined as primary_key. Fixed this discrepency via a hack into the code.
There can be module_params in the playbook which are not part of `add_payload_keys`, but part of `update_payload_keys` in the NITRO_RESOURCE_MAP
For example, `ntpserver` resource has `preferredntpserver` attribute which is not part of `add_payload_keys`, but part of `update_payload_keys`
To make it true desired state, we will update the resource with the module_params
in theprevious commit, the update operation woud run to all modules which has some keys in upload_payload not in add_payload.
It was not considering the params present in the playbook-task.
@sumanth-lingappa sumanth-lingappa merged commit dc76d65 into main Jan 11, 2024
8 checks passed
@sumanth-lingappa sumanth-lingappa deleted the issue-322 branch January 11, 2024 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant