New: Added new CLI option to support better control over managed object names#539
Merged
vscheuber merged 3 commits intorockcarver:mainfrom Feb 17, 2026
Conversation
…t naming used in imports and exports
This was referenced Feb 13, 2026
Contributor
|
@pmckeown this is now available in pre-release Frodo CLI 4.0.0-6 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 is an updated version of this PR which adds a new CLI option to have more control over managed object names in forgeops deployments.
I added an extra commit which adds/updates tests for the changes that @pmckeown added in his commit. I had to create a separate branch/PR from his since I don't have access to his fork, so that's what this PR is for. The old PR can be closed.
I created another PR in the library for fixing a bug I found while creating tests.