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

Allow users to switch provider with GH Actions #214

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

raphaeltm
Copy link
Collaborator

@raphaeltm raphaeltm commented Oct 2, 2024

Samples Checklist

✅ All good!

@raphaeltm
Copy link
Collaborator Author

@lionello I just did this, but now I'm thinking it might be better as a variable for the action... let me know what you think.

@raphaeltm
Copy link
Collaborator Author

On the one hand we can make things a bit more explicit that way. On the other, if they're going to switch providers, then they'll have to use env vars/secrets for all the other provider related stuff anyway...

@raphaeltm raphaeltm requested a review from lionello October 2, 2024 22:23
Copy link
Member

@lionello lionello left a comment

Choose a reason for hiding this comment

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

Looks good, but I'd rather have add an option to the action.

uses: DefangLabs/[email protected]
Copy link
Member

Choose a reason for hiding this comment

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

1.2.0 is the latest

# Use GitHub Variables (https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables)
# to switch between providers. You'll need to make sure to also set the corresponding secrets for the provider you want to use.
DEFANG_PROVIDER: ${{ vars.DEFANG_PROVIDER || 'auto' }}
Copy link
Member

Choose a reason for hiding this comment

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

I think this is fine, but it's the first such variable that we use. Why wouldn't we add it as a param to the action? Seems more explicit that a hidden env var.

@lionello
Copy link
Member

On the one hand we can make things a bit more explicit that way. On the other, if they're going to switch providers, then they'll have to use env vars/secrets for all the other provider related stuff anyway...

Not really. Depends on the provider. For AWS they'd likely use the credentials action.

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