Need info/suggestion on devops process to import operators please.
we are using the deployment manager to deploy our builds to higher environments,
Per requirements we have few service operators been created and have added to product rule that is used in pipeline config for deployment.
however upon deployment these operators were disabled (This is default ) -
we have enabled our operators manually, but during later deployments (we use same pipeline for a given sprint/release based on app requirements),we get aged updates issue because QA has latest timestamp on the operator compared to the dev.
Is there any way to not to disable operators on import.?
After cross checking with our DevOps team came to know that in general we recommend against migrating operators from system to system as it can present a security risk. Deployment Manager is primarily designed around application development and currently does not support any advanced import options in the pipeline.
If you want to accomplish this then you could export the operator records via another product rule and import them, making sure to check off “Enable advanced options…”. Alternatively you could import the operators using the prpcUtils by enabling the below setting during import of operators,
# INSECURE OPERATORS?
# Allows importing operators in an insecure fashion. By default, new operators are disabled when imported,
# and existing operators are not updated. Setting this flag to true will not disable operators
# on import and allow updates of existing operators.