Skip to content

Question - "-exclude" with wildcards #212

Description

@clarkec21

Hi
I am calling utplsql-cli via GitHub Actions on a runner server on OCI as ADMIN user. I pass in multiple schemas to be processed and am writing the documentation to a file and coverage html to a file. My question is: I have a lot of packages to exclude but can I use wildcards in the name so I do not have to exclude so many? For example "FLOW_%" or "FLOW_*"

utplsql run $DATABASE_USER/"$DATABASE_PWD"@$DATABASE_SERVICE -p="ADMIN,APP_OWNER,COM_OWNER" -f=ut_documentation_reporter -o=${GITHUB_WORKSPACE}/utplsql_$JOBNOS.log -f=ut_coverage_html_reporter -o=${GITHUB_WORKSPACE}/coverage_$JOBNOS.html -exclude="FLOW_APEX_ENV,FLOW_APEX_SESSION,FLOW_API_PKG,FLOW_BOUNDARY_EVENTS,FLOW_BPMN_PARSER_PKG,FLOW_CALL_ACTIVITIES,FLOW_CONSTANTS_PKG,FLOW_DIAGRAM,FLOW_ENGINE,FLOW_ENGINE_APP_API,FLOW_ENGINE_UTIL,FLOW_ERRORS,FLOW_EXPRESSIONS,FLOW_GATEWAYS,FLOW_GLOBALS,FLOW_INSTANCES,FLOW_LOGGING,FLOW_MIGRATE_XML_PKG,FLOW_MODELER,FLOW_PARSER_UTIL,FLOW_PLSQL_RUNNER_PKG,FLOW_PLUGIN_MANAGE_INSTANCE,FLOW_PLUGIN_MANAGE_INSTANCE_STEP,FLOW_PLUGIN_MANAGE_INSTANCE_VARIABLES,FLOW_PROC_VARS_INT,FLOW_PROCESS_VARS,FLOW_RESERVATIONS,FLOW_SERVICES,FLOW_SUBPROCESSES,FLOW_TASKS,FLOW_THEME_API,FLOW_TIMERS_PKG,FLOW_TYPES_PKG,FLOW_USERTASK_PKG,FLOW_VIEWER,AUD_OWNER.AOP_API21_PKG,AUD_OWNER.AOP_CONVERT21_PKG,AUD_OWNER.AOP_PLSQL21_PKG,AUD_OWNER.APE_AUD_OWNER.APEX_DATE_RANGE,AUD_OWNER.APE_CRYPTO,AUD_OWNER.APE_DIAGRAM_DATA,AUD_OWNER.APE_DICTIONARY_VIEWS,AUD_OWNER.APE_DOC,AUD_OWNER.APE_INSTALL,AUD_OWNER.APE_INTERFACE,AUD_OWNER.APE_JDOC,AUD_OWNER.APE_JSON_DOC,AUD_OWNER.APE_QA,AUD_OWNER.APE_QA_API,AUD_OWNER.APE_QA_IMPORT_EXPORT,AUD_OWNER.APE_QA_PRINT,AUD_OWNER.APE_QA_RULE_BUILDER,AUD_OWNER.APE_QA_SOURCE,AUD_OWNER.APE_QA_UTILS,AUD_OWNER.APE_SEARCH_ENGINE,AUD_OWNER.APE_UPGRADE,AUD_OWNER.APE_UTILS,AUD_OWNER.APE_XLATE_PKG"

Activity

  1. jgebal commented on Jan 16, 2023

    @jgebal
    Member

    It would definitely be great to have it added.

  2. jgebal commented on Jan 16, 2023

    @jgebal
    Member

    @pesse - any chance for you to have time to make another release?

  3. clarkec21 commented on Feb 3, 2023

    @clarkec21
    Author

    Hi thank you for responding, will there be a release soon?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions