Hi everyone. When using descope's Github import C...
# ask-a-descoper
o
Hi everyone. When using descope's Github import CI/CD action, how do I ignore importing some connectors? I've tried removing the connectors for connectors.json + from the connectors folder, but then It just removed it completetly as part of the import...
r
Hi @Omry Bass To exclude specific connectors from being imported, use the
excludes
parameter in the import API request. The import endpoint accepts an
excludes
array where you can specify which items to skip. For connectors specifically, you would include them in the excludes array rather than removing them from the files. This way, the import process will skip those connectors without deleting them from the target project. Check this: https://docs.descope.com/api/management/projects/import-project
o
@Rahul Rijhwani Thx, what's the format of the format of "excludes"? Do I need to add the connector file's paths?
@Rahul Rijhwani Also, I'm using a github action for it, not an api request
r
Hi @Omry Bass I just confirmed with internal team we are not supporting selective connector import feature.
o
Ok, so what do you suggest I should do in case I have connectors with different configurations per projects?
b
Hi @Omry Bass, Today the GitHub import action (and the underlying snapshot import API) does not support selectively importing or excluding individual connectors. If a connector is present in the snapshot it will be applied to the target project, and if it’s removed from the snapshot it will be deleted from the project, which is why you’re seeing the connector removed when you delete it from
connectors.json
/ the connectors folder. For cases where connectors need slightly different configuration per project (for example, different
baseUrl
or credentials per environment), our recommended approach is to: • Keep a single, shared set of connectors in source control, and • Override the environment-specific fields as part of your CI workflow before running the Descope import. This way you can use the same connector “shape” across projects while keeping the differing configuration in your CI configuration rather than needing to exclude connectors from the import.
o
@Bhagyesh Parna Thxs for the response. What the approach for connectors that only appear in specific projects? For example, I have a DD connector in my prod project, but I don't want it exist in any other language. If I run import to prod right now it will be deleted since the project "beneath it" doesn't contain it
Any other project*
b
Hey @Omry Bass, I see what you're asking for. I asked internally about this to see if we have any feature flag for this. will let you know what I find out!
o
@Bhagyesh Parna Any progress? cc: @Reuven Zabirov
*Update?
b
Hi @Omry Bass, apologies I was on sick leave. Checked internally and it looks like we currently do not have a feature that can do this.