License enforcement changes in om cli #687
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds a new command to the OM CLI that allows users to check for expiring licenses across their Ops Manager installation. The command provides flexibility in checking both staged and deployed products, with customizable time windows for license expiration. Key features: New expiring-licenses command with options for: --staged (-s): Include staged products --deployed (-d): Include deployed products --expires-within (-e): Timeframe to check (default: 3 months) --format (-f): Output format (table/json) Supports checking license expiration across days, weeks, months, and years Returns detailed information including product name, GUID, expiration date, and product state Handles both staged and deployed products with duplicate removal Includes comprehensive test coverage Example usage om expiring-licenses --expires-within 6m --staged --deployed This feature will help operators proactively manage their Ops Manager licenses by identifying products with upcoming license expirations.
yharish991
approved these changes
May 7, 2025
This was referenced May 7, 2025
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new command to the OM CLI that allows users to check for expiring licenses across their Ops Manager installation. The command provides flexibility in checking both staged and deployed products, with customizable time windows for license expiration.
Key features:
expiring-licensescommand with options for:--staged(-s): Include staged products--deployed(-d): Include deployed products--expires-within(-e): Timeframe to check (default: 3 months)--format(-f): Output format (table/json)Example usage
This feature will help operators proactively manage their Ops Manager licenses by identifying products with upcoming license expirations.