Support PulumiPluginJSON.Server in pulumi-java-gen

Open
#711 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

Start in the pulumi-java-gen new build-generation path introduced by #709, then compare it with the old PulumiPluginJSON construction shown in the issue. Trace the schema's PluginDownloadURL into the generated Java resource plugin.json. Done means the generated plugin.json includes the server value so the generated SDK can read it back.

Written by the indexing model from the issue text.

Description

area/plugins kind/enhancement size/S

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

With #709 the responsibility of generating plugin.json with metadata about the package is moving from pulumi-java-gen invocation itself to the generated build system, currently supporting Gradle. One feature lost in translation is populating the server field from PluginDowlnoadURL in the schema.

That is on the old path we have:

		pulumiPlugin := &plugin.PulumiPluginJSON{
			Resource: true,
			Name:     pkg.Name,
			Version:  cfg.Version.String(),
			Server:   pkg.PluginDownloadURL,
		}

We should have the same functionality on the new path. pulumi-java-gen should emit build code that populates PluginDownloadURL from the schema to the generated Java resource plugin.json so the generated SDK code can read it back and act accordingly.

Affected area/feature
Dominant language
Java
Stars
85
Forks
26
Avg merge
11h 49m
Merged PRs (30d)
22

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pulumi/pulumi-java

All issues in pulumi/pulumi-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.