BREAKING CHANGE(schema): split authentication.fields into inputFieds and outputFields (PDE-5589 )

[Natay]

Fixes the issue: authentication.fields are a combination of input fields (e.g. subdomain or API key - which the user needs to enter), and output fields (computed: true - which we expect authentication procedure to return). Coda, Slack

[Natay]

Bit of a weird scenario,

• Leaving fields as is ( not replacing with inputFields ) results in this error

    ✔ package size should not change much (70764 -> 70508 bytes) (248ms)
    basic-auth
Validating project locally
┌────────────────────┬─────────────────────────────────────────────────────────────────┬─────────────────────────────────────────────────────────────────────────┐
│ Property           │ Message                                                         │ Links                                                                   │
├────────────────────┼─────────────────────────────────────────────────────────────────┼─────────────────────────────────────────────────────────────────────────┤
│ App.authentication │ additionalProperty "fields" exists in instance when not allowed │ https://platform.zapier.com/cli_docs/schema#authenticationschema@[16](https://github.com/zapier/zapier-platform/actions/runs/13375926420/job/37355062393#step:5:17).3.0 │

• But updating to inputFields causes this error

 ›   Error: "https://zapier.com/api/platform/cli/check" returned "400" saying 
 ›   "App must validate against schema before running app checks"

Going to reach out to team on best approach here, I think I may need to leave the "fields" as is and update it's description to "DEPRECATED"?

[Natay]

I'll dig up some older PRs to see how fields are deprecated and do the same here

[Natay]

Okay,

• Marked "fields" as deprecated following this PR
• Created a ticket to update example-apps after this MR, from testing I am still getting we Error: "https://zapier.com/api/platform/cli/check" returned "400" if they are updated in this PR. I think this is because the major version needs to be published first but that's a guess.
• Created ticket to remove "authentication.fields"

[kola-er]

@Natay Good start. Reading the requirement again, it seems the auth inputFields and outputFields have some non-common properties as below:

• For the inputFields
  • helpText
  • placeholder
  • choices
  • inputFormat
• For the outputFields
  • isNoSecret
  • computed (however this would be redundant and can be removed)

Apologies for leading you on to use same for both, but we would need to break the /AuthFieldSchema into /AuthInputFieldSchema and /AuthOutputFieldSchema.

Also before this is merged, we need to update the backend to support both auth inputFields and outputFields in addition to the auth fields.

[Natay]

@kola-er thank you!

Would it make sense to include isNoSecret for inputFields as well? Or do we expect things like "api_key" to be in the output only?

• Yes

Also, should we update legacy-scripting-runner as well?

• We should update the examples/tests there.

[Natay]

Backend MR to support inputFields and outputFields

[eliangcs]

zapier invoke is still gaining adoption. It would hurt if it started breaking. So I'd like the invoke command to continue working on previous versions of platform-core for at least some time. Maybe we could do something like:

Suggested change

	appDefinition.authentication.inputFields,
	appDefinition.authentication.fields || appDefinition.authentication.inputFields,

And add this back at line 336-338:

      if (field.computed) {
        continue;
      }