-
Notifications
You must be signed in to change notification settings - Fork 12
Update actions around ephemeral instances to new api surface #31
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
Conversation
|
The ephemeral instance for the application preview has been shut down |
whummer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great to see the progress and next iteration of eph. instances @lukqw ! 🚀 LGTM - just some minor comments / questions, but shouldn't block the merge.. 👍
ephemeral/startup/action.yml
Outdated
| previewName=preview-$prId | ||
| response=$(curl -X POST -d "{\"auto_load_pod\": \"${AUTO_LOAD_POD:-${{ inputs.auto-load-pod }}}\"}" \ | ||
| response=$(curl -X POST -d "{\"instance_name\": \"${previewName}\", \"env_vars\": {\"AUTO_LOAD_POD\": \"${AUTO_LOAD_POD:-${{ inputs.auto-load-pod }}}\", \"EXTENSION_AUTO_INSTALL\": \"${EXTENSION_AUTO_INSTALL:-${{ inputs.extension-auto-install }}}\"}}"\ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: This is pretty dense syntax, maybe we could pull the conditional assignment for AUTO_LOAD_POD / EXTENSION_AUTO_INSTALL into temporary variables?
Also, just to confirm - do we want the inputs.* values to be the fallback (if the env variables are not defined), or rather the other way around, i..e, have them overwrite the env. variables, if configured? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Waldemar Hummer <waldemar.hummer@gmail.com>
Context
Moving ephemeral instances to the preview stage has introduced a few changes to the API.
This PR adjusts the actions around ephemeral instances to integrate with those changes.
Testing
I have introduced a separate api key from staging to verify functionality against the currently deployed application on staging.
Before merging this has to be cleaned up again, i.e. switching back to the production api key for the test suite, and calling the production endpoint in the action.
Questions
@lakkeger do I need to add the
extension-auto-installandauto-load-podarguments to the existing root action?