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

Update get_register_command to reflect new mandatory fields #1095

Conversation

Gauravtalreja1
Copy link
Collaborator

(cherry picked from commit 064530e)
Cherrypick of PR: #1087

Description

  • Update get_register_command to reflect new mandatory fields i.e ActivationKey, which was previously operating systems.
  • Make get_register_command work when no values are passed, required for default values validation and few negative tests.
  • Add locator for new_activation_key_link, which appears when no AK available in organization, and when there's single AK in organization, AK will be auto-selected in 6.15+ but for 6.14.z it should be filled manually.

…eQE#1087)

Signed-off-by: Gaurav Talreja <[email protected]>
(cherry picked from commit 064530e)
Signed-off-by: Gaurav Talreja <[email protected]>
@Gauravtalreja1 Gauravtalreja1 added No-CherryPick PR doesnt need CherryPick to previous branches 6.14.z labels Dec 20, 2023
@Gauravtalreja1 Gauravtalreja1 self-assigned this Dec 20, 2023
@Gauravtalreja1 Gauravtalreja1 changed the title Update get_register_command to reflect new mandatory fields (#1087) Update get_register_command to reflect new mandatory fields Dec 20, 2023
@Gauravtalreja1
Copy link
Collaborator Author

PRT passed on SatelliteQE/robottelo#13536

@adarshdubey-star adarshdubey-star merged commit 04d3a4c into SatelliteQE:6.14.z Dec 20, 2023
10 checks passed
@Gauravtalreja1 Gauravtalreja1 deleted the update-get-register-command-614z branch December 20, 2023 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.14.z No-CherryPick PR doesnt need CherryPick to previous branches
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants