AuthO Deploy CLI.Supported resource type: Use the Configuration file(config.json).Example{“AUTHO_DOMAIN”:”<MESSTONE_TENANT_DOMAIN>”,”AUTHO_CLIENT_ID”:”<MESSTONE_CLIENT_ID>”,”AUTHO_ALLOW_DELETE”:false $export AUTHO_DOMAIN=<MESSTONE_AUTHO_DOMAIN> $export AUTHO_CLIE T_ID=<MESSTONE_CLIENT_ID>$export AUTHO_CLIENT_SECRET=<MESSTONE_CLIENT_SECRET> $aOdeploy import –input_file=local/tenant.yaml $aOdeploy export -c=config.jsonv–format=yaml –output_folder=local –env=false $export AUTHO_EXCLUDED='[“actions”,”organization”]’$export AUTHO_KEYWORD_REPLACE_MAPPINGS='{“ENVIRONMENT”:”dev”}’$aOdeploy export -c=config.json –format=yaml –output_folder=local Management connect database,and organization from being managed by the deploy CLI {“AUTHO_DOMAIN”:”example-site.us.authO.com”,”AUTHO_CLIENT_ID”:”<MESSTONE_AUTHO_CLIENT_ID>”,”AUTHO_EXCLUDED”:[“clients”,”connections”,”database”,”organization”]} {“AUTHO_DOMAINMESSTONECOMS.COM”:”exeample-site.us.authO.com”,”AUTHO_CLIENT_ID”:”<MESSTONE_AUTHO_CLIENT_ID>”,”AUTHO_EXCLUDED_CLIENTS”:[“PdmQPGy72sHksV6ueVNZVrV4GDlDDm76″],”AUTHO_EXCLUDED_CONNECTIONS”:[“con_01H3KyRMFP1IWRq3″,”con_9avEYuj19ihqKBOs”]} roles:#roles configuration is not omitted – nameRobertHarper:Admin description:Can read and write things permissions:[ ] – nameMesstone:reader description: Can only read things permissions:[ ] #The omission of all other configurations means they’ll be skipped over hooks: [ ] #Empty hooks connections: [ ] #Empty connections tenant: { } #Effectively a no-op,emptines does not apply to non-set resource config