Forum Discussion

MJ_1024's avatar
MJ_1024
Icon for Cirrus rankCirrus
Apr 03, 2026

Changes to DO and AS3 GitHub - no longer monitored

I see Changes to DO and AS3 GitHub pages have been updated with these notices: " AS OF FEBRUARY 2026, THIS GITHUB REPOSITORY WILL NO LONGER BE MONITORED OR UPDATED. This repository will remain a...
devops
Juergen_Mang's avatar
Juergen_Mang
Icon for MVP rankMVP
Jun 25, 2026

I now tried the schema files from the rpm itself. The structure is not the same and it unfortunately does not work in my setup.

My declarations look like:

{
    "$schema": "https://raw.githubusercontent.com/F5Networks/f5-appsvcs-extension/main/schema/latest/as3-schema.json",
    "class": "AS3",
    "action": "deploy",
    "persist": true,
    "declaration": {
        "class": "ADC",
        "schemaVersion": "3.55.0",
        "tenant": {
        }
    }
}

 

In the rpm there are 4 schema files:

  1. adc-schema.json
  2. app-schema.json
  3. as3-request-schema.json
  4. settings-schema.json

 

But validation and autocompletion don't work with any of these. It seems the published schema on GitHub is some sort of combination of all of this files?

I opened a ticket for this.

Juergen_Mang's avatar
Juergen_Mang
Icon for MVP rankMVP
Jun 25, 2026

I got an answer: The schema on GitHub is created at build time of the AS3 package from the files above. There are not a 1:1 replacement for the schema file that was hosted on GitHub. Support gave me an up-to-date schema file.

I think for DO it is the same.

Looks like the current flow is to open a support ticket for each new released AS3 or DO version to get the schema files.

The easiest solution would be that this schema files are downloadable like the AS3 package itself.