-
Notifications
You must be signed in to change notification settings - Fork 36
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
add fixKeys command / CSCLSROZ-29 #38
Comments
@phjulia - maybe interesting for you? |
@JoernBerkefeld #1
mcdev fixKeys Project/BU type key
#2
mcdev fixKeys Project/BU type
#3
mcdev fixKeys Project/BU (3) would update the key to match the name in of all metadata of all types (where key can be updated) |
Took the liberty of adding some formatting to your Post ;-) Yes, in principle like that. Without Also, we should probably enforce a full retrieve of the chose type as a first part of what fixKeys does. |
Closed by #1022. |
Closed by #1062. |
Closed by #1064. |
should work just by allowing the 2 options because fixKeys uses deploy method internally
…te for already scheduled automations
Closed by #1067. |
add fixKeys command that re-uses the --changeKeyField logic together with this.definition.nameField
this is a basic wrapper around --changeKeyField that searches for metadata of the given type with name/key mismatches.
Acceptance Criteria:
out of scope:
basic steps:
metadata[(this.definition.keyField] !== metadata[(this.definition.nameField]
)deploy cred/bu type --fromRetrieve --changeKeyField=${this.definition.nameField}
on found keys for selected typelib\MetadataTypeDefinitions.js
to check array inx.definition.dependencies
for matches with the selected type... the user then has to git add / commit & push on their own.
The text was updated successfully, but these errors were encountered: