build: deploy resource provider #184
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AquiGorka
force-pushed
the
gorka/build-deploy-resource-provider
branch
15 times, most recently
from
3d295c5 to
f68a974
Compare
AquiGorka
force-pushed
the
gorka/build-deploy-resource-provider
branch
2 times, most recently
from
048a0e7 to
8bcf544
Compare
AquiGorka
requested review from
walkah,
10d9e,
richardbremner,
bgins,
noryev and
taoshengshi
bgins
pushed a commit
that referenced
this pull request
Jun 25, 2024
* build: add job for deploying rp * fix: resource provider dockerfile lilypad service run in background
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Review Type Requested (choose one):
Summary
These changes add the deploy script for the testnet CPU resource provider (make sure at least there is one RP that can run
cowsay)Task/Issue reference
Closes: #141
Details (optional)
For whatever reason, I could not get this to work with
doppler, if I injected the doppler envs as a file for run the private key was not used 🤷 so I went with the approach of adding it to the secrets in github.How to test this code? (optional)
Tested while I created the PR, if you are reading this, I've already made sure the deploy works and we already have an instance in AWS and I was looking at the solver logs and can verify this deploy incremented the number of resource offers (7 at this time)