Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automation API Proof of Concept [DO NOT MEERGE] #1180

Closed
wants to merge 4 commits into from

Conversation

pawelprazak
Copy link
Contributor

Description

A minimal PoC for Automation API aimed at sparking conversation around moving this effort forward.

Goals:

  • prove it is doable and not very hard
  • help to assess the scope of changes to existing SDK
  • help to estimate cost of completing this feature

Non-goals:

  • not a complete implementation
  • not optimized for in-depth code review

Proposed next steps:

  • identify complete list of required refactorings in existing SDK that are required (or useful) for Automation API
  • gather community input regarding the API (esp. asynchronous API, executors, context propagation, etc.)
  • gather team feedback on the implementation details required to successfully finish the Automation API

Relates to #965

Checklist

  • I have added tests that prove my fix is effective or that my feature works
  • Yes, there are changes in this PR that warrants bumping the Pulumi Service API version

@pawelprazak pawelprazak requested a review from t0yv0 August 9, 2023 13:45
ctx.export("exp-secret", Output.of(ctx.config().requireSecret("buzzz")));
};

var workspace = PulumiAuto
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here is the minimal example of how the API could look like :)

@t0yv0 t0yv0 requested a review from justinvp August 9, 2023 13:54
@t0yv0
Copy link
Member

t0yv0 commented Aug 10, 2023

Hey @pawelprazak thank you for this contribution! Is there a chance to publish this from a Virtus repo so it's a standalone artifact as opposed to something checked in here? Would you need changes to the core Java SDK here to support the Automation API? Our teams are operating with very limited cycles right now to take on more maintenance (accept this contrib).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants