fr-config-pull skips GROOVY scripts during script export

[brandon-barnes]

fr-config-pull currently appears to skip AM/AIC scripts where language is GROOVY.
AM supports both JavaScript and Groovy scripts, but the current script export logic only persists scripts where:

script.language === "JAVASCRIPT"

This means Groovy scripts that are visible and active in the AIC admin UI are omitted from the exported config repository.

Observed impact:

• Groovy scripts are not written under scripts-content.

• Their corresponding JSON config is not written under scripts-config.

• A Git-backed config export can appear complete while missing valid tenant scripts.

• This affects at least SOCIAL_IDP_PROFILE_TRANSFORMATION scripts, but may affect any Groovy-backed script context.

Expected behavior:

• JAVASCRIPT scripts export as .js.

• GROOVY scripts export as .groovy.

• Both script types should have corresponding config JSON files in scripts-config.

Potential implementation approach:

const SCRIPT_EXTENSIONS = {
  JAVASCRIPT: "js",
  GROOVY: "groovy",
};

Then use the script language to choose the exported file extension instead of filtering out non-JavaScript scripts.
Related observation:

• In packages/fr-config-pull/src/scripts/journeys.js, script dependency exports appear to call exportScriptById(...) without await. If dependency export is asynchronous, referenced scripts may race process completion and fail to land reliably during journey export.

Suggested changes:

• Remove the JavaScript-only export filter.

• Add supported-language-to-extension handling for JAVASCRIPT and GROOVY.

• Await exportScriptById(...) calls in journey dependency export.

• Add tests for JavaScript, Groovy, and unsupported script language handling.

[brandon-barnes]

I reproduced this against a tenant with an active SOCIAL_IDP_PROFILE_TRANSFORMATION script using:

• _id: redacted
• language: GROOVY
• context: SOCIAL_IDP_PROFILE_TRANSFORMATION

The script was visible in the AIC admin UI and retrievable directly by script ID, but did not appear in the normal fr-config-pull output.

A local patch that mapped script language to file extension produced the expected export:

• JAVASCRIPT -> .js
• GROOVY -> .groovy

I also noticed that journey dependency script export calls exportScriptById(...) without await, so referenced scripts may not be reliably written before journey export completes.

[kevswiss]

Hi Brandon, thanks for flagging this. The filter was a conscious decision, since AIC only supports JavaScript. I appreciate that the out of the box social idp transformation scripts are still groovy, but any custom scripts should be written in JS

[brandon-barnes]

Hi Brandon, thanks for flagging this. The filter was a conscious decision, since AIC only supports JavaScript. I appreciate that the out of the box social idp transformation scripts are still groovy, but any custom scripts should be written in JS

Thanks, that tracks with the current AIC position. I also found the Ping deprecation notice for Groovy OIDC custom claims scripts, which shows that Groovy support for that use case reached EOL on April 20, 2022:

https://docs.pingidentity.com/pingoneaic/product-information/deprecation-notices.html#groovy-oidc-custom-claims-script

Given that, I agree it probably does not make sense for fr-config-manager to treat Groovy as a supported custom-script authoring/import path.

My concern is specifically the silent omission behavior during export. If a Groovy-backed script object still exists in a tenant and is visible/retrievable through AM APIs, fr-config-pull currently makes the exported script inventory look complete while omitting that object.

Would you be open to one of these instead?

• emit a warning when non-JavaScript script objects are discovered and skipped;
• document that script export intentionally excludes non-JavaScript scripts;
• optionally include read-only metadata for skipped scripts, without exporting/importing executable Groovy content.

That would make the behavior clear without implying Groovy is supported for new/custom AIC scripting.