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.

Sign up for GitHub

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

Jump to bottom

Use region code instead of name to deploy in non-default Vultr region. #14713

Merged
merged 1 commit into from
Apr 1, 2024
Merged

Use region code instead of name to deploy in non-default Vultr region. #14713

merged 1 commit into from
Apr 1, 2024

Conversation

matthewhall79
Copy link
Contributor

Description

Use region code instead of name to deploy in non-default Vultr region.

Motivation and Context

Fixes #14712

How Has This Been Tested?

Successfully deployed to Vultr's London region.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • My code follows the code style of this project.
  • [] My change requires a change to the documentation.
  • [] I have updated the documentation accordingly.
  • [] I have added tests to cover my changes.
  • [] All new and existing tests passed.

@CLAassistant
Copy link

CLAassistant commented Mar 30, 2024 •
edited
Loading

CLA assistant check
All committers have signed the CLA.

@jackivanov jackivanov enabled auto-merge (squash) April 1, 2024 01:17
@jackivanov jackivanov merged commit 6ce6f5c into trailofbits:master Apr 1, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jackivanov jackivanov jackivanov approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Error creating Vultr server in non-default region
3 participants
@matthewhall79 @CLAassistant @jackivanov