GCN candidate

[ezzarghili]

Graal Cloud Native GCN is an open source project (https://github.com/oracle/gcn) for cloud-native microservices. First version we are submitting as PR, we will follow the vendor API process for future releases.

[ezzarghili]

First release artifacts are published now and can be now consumed by users using sdkman when these change are merged.

[marc0der]

All our Java and Graal versions are published by an automated process consuming the Disco API. Perhaps we can leverage this instead? /cc @eddumelendez

[ezzarghili]

For GraalVM releases, once we onboard the vendor API we can also take over publishing new releases including non community ones that are not yet available on SDKMAN

For this PR, it is not about GraalVM, people will still need to install GraalVM separately, this change is for CLI tool of GCN that allow people to generate projects and interact with their GCN codebase.

[eddumelendez]

After running sdk update the candidate is listed sdk list gcn

[ezzarghili]

@eddumelendez I based my changes on existing code that suggest tag.gz are used too (e.g src/main/scala/io/sdkman/changelogs/JdkMissionControlMigrations.scala)

Testing now it seems that we are required to use zip archives?

Should we move this to use zip for all platforms?

[marc0der]

@ezzarghili yes, we only allow tarballs in special cases for now. Some work is on the way to allow both, but is not ready yet. For now zips are preferable. Will you also be using our vendor API? If so, you can use the PATCH method to change versions without needing database migrations.

[ezzarghili]

Thank you @marc0der, I sent my public key for the vendor API access credentails, will use the API to fix this.

[ezzarghili]

@marc0der any idea when to expect the access credentials? thanks