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

[Integration][omevv_baseline_profile] - Create, Modify and Delete #767

Open
wants to merge 13 commits into
base: collections
Choose a base branch
from

Conversation

rajshekarp87
Copy link
Contributor

@rajshekarp87 rajshekarp87 commented Nov 13, 2024

Description

A few sentences describing the overall goals of the pull request's commits.

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #

ISSUE TYPE

  • Bugfix Pull Request
  • Docs Pull Request
  • Feature Pull Request
  • Test Pull Request
COMPONENT NAME
OUTPUT

ADDITIONAL INFORMATION

Checklist:

  • I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
  • I have verified that new and existing unit tests pass locally with my changes
  • I have not allowed coverage numbers to degenerate
  • I have maintained at least 90% code coverage
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • I have maintained backward compatibility

@ansible-collections-svc
Copy link
Collaborator

Can one of the admins verify this patch?

@rajshekarp87 rajshekarp87 self-assigned this Nov 14, 2024
@rajshekarp87 rajshekarp87 added the validation/in-progress Validation is in progress label Nov 14, 2024
@rajshekarp87 rajshekarp87 added this to the v9.9.0 milestone Nov 14, 2024
@rajshekarp87 rajshekarp87 force-pushed the integration/omevv_baseline_profile branch from f512504 to 4c0788c Compare November 15, 2024 10:23
name: OMAM_Baseline_Profile
repository_profile: OMAM_Firm_Repo
cluster:
- OMAM-Cluster-1
Copy link
Contributor

Choose a reason for hiding this comment

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

why are we hardcoding cluster name, are we in assumption all the OMEVV setup has same cluster name, please check once.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This will be prerequisite before running the suite

Copy link
Contributor

Choose a reason for hiding this comment

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

as we discussed we should have dynamic fetching of cluster name as OMEVV has API to fetch it

@ABHISHEK-SINHA10
Copy link
Contributor

Please add negative scenarios, I think it's missing.

that:
- cm_dm_result_baseline.changed
- 'cm_dm_result_baseline.msg == "Changes found to be applied."'
- cm_dm_result_baseline.diff.before | length > 1
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we compare the fields instead of just length.

@rajshekarp87 rajshekarp87 added validation/completed Validation is completed and removed validation/in-progress Validation is in progress labels Nov 21, 2024
@ABHISHEK-SINHA10
Copy link
Contributor

ABHISHEK-SINHA10 commented Nov 21, 2024

please add negative scenarios for create, modify and delete too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
validation/completed Validation is completed
Projects
Development

Successfully merging this pull request may close these issues.

4 participants