Provide a way to exclude all of an object during a0deploy import

Describe the problem you’d like to have solved

I would like to be able to exclude all of certain configuration objects during import without having to specify individual values. This is especially true of Enterprise connections. Currently, I have to specify the following in my import config to avoid importing them:

  "AUTH0_EXCLUDED_CONNECTIONS": [
        "9395127f-4853-4842-8c2b-2be4135fa89",
        "9563eb0b-accc-489d-b03c-f6373d0ed0a",
        "f0272ae7-9fea-4e0a-b856-9b360250b5a",
        "9cab3ff8-ff15-410a-b8b9-816a7151b4f",
        "614d9405-77c1-4239-bdda-4ca306bd36c",
        "89af4988-4d68-476c-b4c6-c476835088f",
        "test"
   ]

This is error prone and burdensome to maintain.

Describe the ideal solution

I would like the CLI to support wildcards. Here are two examples.

Exclude all connections

  "AUTH0_EXCLUDED_CONNECTIONS": [ "*" ]

Exclude some based on partial name match.

  "AUTH0_EXCLUDED_CONNECTIONS": [ 
    "test*",
    "expermiental*"
 ]

Alternatives and current work-arounds

My only alternative right now is to explicitly list every connection I want to exclude.

[willvedd]

@stuarthadfieldglobality Appreciate your interest in the library and for providing your feedback!

I absolutely agree that resource exclusion is a bit of a sore spot with this project. It should be a first-class feature of this utility and until now hasn’t gotten the attention it deserved. The three issues you referenced above are just the ones that are open, there are several other closed duplicates.

Speaking candidly here, this repo just recently got more formal resourcing and attention, which means that our team is still finding our bearings in terms of stability and roadmap. Progress is modest but rest assured we’re doing our best to identify the highest impact work, this issue included.

FWIW, I’m looking into a more formal method of exclusion as we speak. I still won’t provide a firm date, but I hope that you can hold patient for another week because I’d really like to get your feedback on a proposal I’m drafting.

In terms of workarounds, I regretfully have no suggestions other than adopting the Auth0 Terraform Provider. If you already use Terraform in your development workflows, it should be a frictionless method of managing your config.

[benwozniak]

+1 would love to see this, the “EXCLUDED_PROPS” section unfortunately does not work. I am trying to import my tenant but cannot because of enterprise connections.